Details
-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
-
2
-
Description
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Current Behavior
Automation "when a linked issue is transitioned" is not triggered if the transition does not result in the change of the issue status. Examples of transitions that do not change status include:
- Initial "Create" transition
- Transitions that loop back to the same status
Suggested Behavior
When linked issue automation rule should be triggered by any transition including the create transition and other transitions that do not result in status change.
Use case:
For example a service desk admin may not want an agent to put a service desk request into waiting on dev unless a dev ticket is created. They could add a condition to the transition so that only a certain user or group can transition the request to waiting for dev. Then they create an automation rule that automatically transitions the service desk request into waiting for dev as soon as the dev.
- For example the agent may use the "Create Linked Issue" menu option to create the linked issue directly from the JIRA Service Desk request.
Workaround
Create another status so outgoing transition from that status is evaluated.
Attachments
Issue Links
- is caused by
-
JSDCLOUD-5069 Automation blueprint not evaluating when source issue is "initially" transitioned.
- Closed
- relates to
-
JSDSERVER-4517 Misleading terminology in JSD automation "A linked issue is transitioned"
- Gathering Impact
-
JSDCLOUD-3993 Automation WHEN linked issue should be triggered by transitions without status change
- Closed