Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
6.4.13, 7.3.0, 7.2.3, 7.12.3
-
6.04
-
31
-
Severity 2 - Major
-
4
-
Description
Steps to Reproduce:
- Create a Project Management project for the test named PM for example.
- Create another Administrator user called "Admin"
- Create a webhook and set the JQL:
project = PM AND assignee = admin
- Navigate to JIRA Administration > Issues > Workflow
- Edit "PM: Project Management Workflow"
- Change to "Text" view and click on "Start Progress"
- Move to "Post Function" tab and make sure the post function below exist:
Assign the issue to the current user. Please note that the issue will only be assigned to the current user if the current user has the 'Assignable User' permission.
- Add another post function and choose "Trigger a Webhook" to select the previous webhook.
- Move it to the bottom in order to make it the last to be triggered and publish the workflow.
- Login as "admin", create an issue in PM project and click the "Start Progress" button transition.
Expected Result:
With the ticket is updated its assignee to the user that triggered the transition and re-indexed, the webhook will be triggered in the last with the issue met the JQL requirement.
Actual Result:
The webhook is not triggered.
Notes:
Webhook will be the example for the behavior, another case will be Hipchat ticket linked below. It appears to me that the change is only happening after all the last Post Function rule. With the result where the Webhook is not triggered, it means that the Post Function Rule did not run independently as the Webhook Rule did not catch the change of the assignee. The database changes will happen after all the rule triggered it seems.
Attachments
Issue Links
- is related to
-
HCPUB-628 Using JIRA workflow transition screens to modify Assignee does not trigger HipChat notifications filtered for assignee
- Closed
-
JRACLOUD-69927 Webhook triggered by workflow transition does not work if JQL is defined
- Closed
- is superseded by
-
JRASERVER-67860 WebHook JQL should be checked upon transition completion
- Gathering Impact
- relates to
-
JRASERVER-31699 Webhook won't fire on Issue Created if a JQL is provided
- Closed
-
JRASERVER-31966 Unable to define JQL for a Webhook
- Closed
-
JRASERVER-60518 WebHooks not firing when the event triggered is Workflow post function
- Gathering Impact
-
JRASERVER-62528 Webhooks do not fire when creating sub-task or clone issue via post function
- Gathering Impact