-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
2
-
Summary
The JSON data posted by webhooks for any comment or worklog events only contains the issue id. Here is an example
{
"timestamp":1507645154921,
"webhookEvent":"worklog_created",
"worklog":{
"self":"http://jira.com/rest/api/2/issue/999999/worklog/3340413",
"author":{
"self":"http://jira.com/rest/api/2/user?username=admin",
"name":"admin",
"key":"admin",
"emailAddress":"admin@email.com",
"avatarUrls":{
"48x48":"http://jira.com/secure/useravatar?avatarId=10122",
"24x24":"http://jira.com/secure/useravatar?size=small&avatarId=10122",
"16x16":"http://jira.com/secure/useravatar?size=xsmall&avatarId=10122",
"32x32":"http://jira.com/secure/useravatar?size=medium&avatarId=10122"
},
"displayName":"xxxxxxxxxxxxxx",
"active":true,
"timeZone":"Europe/Berlin"
},
"updateAuthor":{
"self":"http://jira.com/rest/api/2/user?username=admin",
"name":"admin",
"key":"admin",
"emailAddress":"admin@email.com",
"avatarUrls":{
"48x48":"http://jira.com/secure/useravatar?avatarId=10122",
"24x24":"http://jira.com/secure/useravatar?size=small&avatarId=10122",
"16x16":"http://jira.com/secure/useravatar?size=xsmall&avatarId=10122",
"32x32":"http://jira.com/secure/useravatar?size=medium&avatarId=10122"
},
"displayName":"Administrator",
"active":true,
"timeZone":"Europe/Berlin"
},
"comment":"Adding a worklog",
"created":"2017-10-10T16:19:14.921+0200",
"updated":"2017-10-10T16:19:14.921+0200",
"started":"2017-10-10T16:18:00.000+0200",
"timeSpent":"5h",
"timeSpentSeconds":18000,
"id":"3340413",
"issueId":"999999"
}
}
Suggestion
It should return project information such as projectId and projectKey as well, and also issue information such as issue type, etc
Notes
Due to JRASERVER-59980, JQL filter doesn't work for worklog and comment events. Having them return these information will make it easier to parse the information to perform actions on necessary issues
- relates to
-
JRASERVER-59980 JQL filter for Webhooks doesn't work correctly when "Comment" and "Worklog" related events are fired - CVE-2017-18104
-
- Closed
-
-
- Closed