Service Desk issue fails to transition when linked issues change status

Marc Eiler June 13, 2016

I have an instance of Service Desk and another instance of another project set as a SCRUM type. What I'm trying to do is create a linked issue from the SD issue from the field to an issue in the backlog of the SCRUM project. When the Status of the SCRUM issue is created, I want the SD issue to automatically get transitioned to the Approved status. When the SCRUM issue is transitioned to the Done status, I want the SD issue to transition to the Resolved status. I know that the SCRUM project is configured correctly. We've been using it for quite a while now. I'm not understanding why the automation configuration that I have for the SD project is not working properly. There are only 2 rules created and they don't conflict with each other since they do entirely different things.

Here's the process and validations that I'm doing:

The automation rule:

  • Rule type: A linked issue is transitioned
  • When: A linked issue is transitioned
  • If: Linked issue matches: Status = Ready
  • Then: Transition issue = Approve
  • Else If: Linked issue matches: Status = Done
  • Then: Transition issue = Resolved

Steps I'm going through

  • Create a new Service Desk bug issue from a customer
    • Includes a subject and description as required
    • Automatically gets assigned an approver
    • The issue is created in the Needs Approval status
  • Create a linked bug issue from the issue details to the SCRUM project by clicking More -> Create Linked Issue
    • Set the link type to Is Caused By
    • Issue created in Ready status
  • Verified that the SD issue is still in Needs Approval status despite the first condition in the automation rule
  • Transitioned the SD issue to Approved (Waiting for Support status)
  • Transitioned SCRUM issue to Done status
  • Verified that the SD issue is still in the Waiting for Support status despite the second condition in the automation rule

I've tried to delete and recreate the rule to no avail. This is using the Cloud instance of JIRA and Service Desk. The account that is set to run the automation is my own account which is a full admin of the site and all products. All steps can be done manually by me, so I have confirmed that there are no issues with my permissions.

 

2 answers

0 votes
Christopher Gronde December 20, 2017

I am having a similar issue with this same type of rule.  I am on the server instance and it still doesn't work.

0 votes
Mahesh S
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 14, 2016

Please verify the below steps.

           when SCRUM issue moves to Ready status,

  • Go to Scrum workflow and look for the the transition step to Ready status.
  • Add a post function in 'Transition Linked Issues' and chose the link type. (Note: you should choose the reverse link type to 'Is Caused By' from scrum's perspective). Add the Approved status for auto transition.

    Similarly when SCRUM issue moves to Done status,
  • Go to Scrum workflow and look for the the transition step to Done status.
  • Add a post function in 'Transition Linked Issues' and chose the link type. Add the Resolved status for auto transition.

This could be done via a simple scripted post function. However, the script runner wont be available in the cloud JIRA  instance. Hope, you will have this functionality ''Transition Linked Issues'' in JIRA cloud.

Marc Eiler June 14, 2016

I have the Cloud instance, so this won't work for me. Any other ideas? Thanks.

Suggest an answer

Log in or Sign up to answer