How do you stay on top of your work when it is scattered across multiple Atlassian products? "If only there was a single place where I could see all my activity..." - sounds familiar? We are going to provide you an insight into what lead to the creation of a new Activity API. Following last year’s Atlas Camp announcement from our CTO Sri Viswanath, Atlassian is moving onto GraphQL - new Activity API is one the first pieces of the GraphQL Atlassian Platform and is the technology behind start.atlassian.com. Join Sergey Meshkov, Senior Developer, who will provide you a sneak peek of the new GraphQL Activity API as it will soon be available to our vendors.

1. SERGEY MESHKOV | SENIOR DEVELOPER | ATLASSIAN
Activity API
Access to User Activities

2. COLLABORATIVE WORK

7. USER ACTIVITIES

8. Access to
User
Activities?
No single place

9. Access to
User
Activities?
No single place
No consistency

10. Access to
User
Activities?
No single place
No consistency
No shared experience

11. Convergence of work
Access User Activity from a single place

12. Show me all issues assigned to
Team Rocket
ACTIVITY
API
Show me all pages created by
Norah
Show me all objects worked on
Site A
Show me recent blogs published
in all Confluence instances

14. GraphQL is a query language
for APIs and a runtime for
fulfilling those queries with
your existing data.
GRAPHQL.ORG

15. Many
endpoints,
one per use
case.
Single
endpoint for
all use cases.
GRAPHQL REST

16. Server
controls
response
data.
Client defines
the data it
wants in the
response.
GRAPHQL REST

17. Evolves with
endpoints
and
schemas.
Evolves by
updating
schema.
GRAPHQL REST

18. {
myActivities {
workedOn
viewed
all
}
}
ACTIVITY API - QUERY

19. {
myActivities {
workedOn(…)
viewed(…)
all(…)
}
}
ACTIVITY API - QUERY

20. {
myActivities {
workedOn(filter: {. . .}, first: <N>)
viewed(filter: {. . .}, first: <N>)
all(filter: {. . .}, first: <N>)
}
}
ACTIVITY API - QUERY

21. https://start.atlassian.com

22. https://start.atlassian.com
Activity types

23. https://start.atlassian.com
Activity objects

24. https://start.atlassian.com
Collaborators

25. https://start.atlassian.com
Time

26. https://start.atlassian.com

27. {
myActivities {
viewed
. . .
ACTIVITY API - QUERY

28. {
myActivities {
viewed {
nodes {
object
. . .
ACTIVITY API - QUERY

29. {
myActivities {
viewed(first: 10) {
nodes {
object
. . .
ACTIVITY API - QUERY

30. {
myActivities {
viewed(first: 10) {
nodes {
object {
name
}
. . .
ACTIVITY API - QUERY

31. {
"data": {
"myActivities": {
"viewed": {
"nodes": [
{ "object": { "name": "TASK-5 Re-index cluster" } },
{ "object": { "name": "Meeting notes" } },
. . .
]
. . .
}
}
ACTIVITY API - RESULT

32. https://start.atlassian.com

33. https://start.atlassian.com

34. {
myActivities {
viewed(first: 10) {
nodes {
object { name url }
. . .
ACTIVITY API - QUERY

35. {
myActivities {
viewed(first: 10) {
nodes {
object { name url }
timestamp
. . .
ACTIVITY API - QUERY

36. {
myActivities {
viewed(first: 10) {
nodes {
object { name url }
timestamp
contributors { profile { picture } }
}
}
}
}
ACTIVITY API - QUERY

37. {
"data": {
"myActivities": {
"viewed": {
"nodes": [
{
"object": {
"name": "TASK-5 Re-index cluster",
"url": "https://…",
},
"timestamp": "2019-08-24T06:40:56.129Z",
"contributors": [ { "profile": { "picture":
"https://…" } },
ACTIVITY API - RESULT

39. {
myActivities {
all
. . .
ACTIVITY API - QUERY

40. ACTIVITY API - QUERY
{
myActivities {
all(filter: { . . . }) {
. . .

41. ACTIVITY API - QUERY
{
myActivities {
all(filter: {
products: [ JIRA_SOFTWARE ],
. . .
}) {
. . .

42. ACTIVITY API - QUERY
{
myActivities {
all(filter: {
products: [ JIRA_SOFTWARE ],
objectTypes: [ ISSUE ],
. . .
}) {
. . .

43. ACTIVITY API - QUERY
{
myActivities {
all(filter: {
products: [ JIRA_SOFTWARE ],
objectTypes: [ ISSUE ],
eventTypes: [ ASSIGNED ]
}) {
. . .

44. ACTIVITY API - QUERY
{
myActivities {
all(filter: {
products: [ JIRA_SOFTWARE ],
objectTypes: [ ISSUE ],
eventTypes: [ ASSIGNED ]
}, first: 5) {
. . .

45. ACTIVITY API - QUERY
{
myActivities {
all(filter: {
products: [ JIRA_SOFTWARE ],
objectTypes: [ ISSUE ],
eventTypes: [ ASSIGNED ]
}, first: 5) {
nodes {
object { name }
}
}
. . .

46. ACTIVITY API - RESULT
{
"data": {
"myActivities": {
"all": {
"nodes": [
{ "object": { "name": "CLEM-956 Check …" } },
{ "object": { "name": "CLEM-1761 UI: …" } },
. . .
]
. . .
}
}

47. ACTIVITY API - QUERY
nodes {
object
contributors
timestamp
eventType
. . .
}
object {
id
name
type
product
cloudID
url
iconURL
. . .
}
contributors {
lastAccessedDate
profile {
accountId
name
picture
}
. . .

48. Powerful Flexible Universal Cloud
Takeaways

49. One more thing

50. Activity API powers Activity
Streams for Forge enabling
developers to setup triggers
around User Activity.

51. SERGEY MESHKOV | SENIOR DEVELOPER | ATLASSIAN
Thank you!