Post Function to transition Issue linked using "Parent Link" based on the Transition of an issue typ

Devi karthikeyan

Hi, I have the following hierarchy defined,

Initiative -> Feature -> Epic -> All other Standard Issue Types -> All Sub-Task issue types

I am implementing post function to get higher hierarchy to transition based on the Lower hierarchy issues transition.

I managed to get it going smooth till Epic Level where the default linking is applied.

From Epic to Initiative we use "Parent Link" field from Portfolio Plugin to get the linking done.

Now, I need your help to get the Transition of Initiative based on the Transition of Feature and Transition of Feature based on the Transition of Epic.

Please provide help based on the available default option or based on the JSU, If possible help with Script runner script to implement this.

I know i am expecting too much from you guys but i am helpless without you people.

Earl McCutcheon

Hello @Devi karthikeyan ,

Natively there is not a way to do this, however there is an option using Automation for Jira , with a note for anyone on the Jira cloud platform that finds this thread this will currently only work on the Server platform as the needed JQL functions are not avaliable in Jira Cloud at this time, please vote for the following Request if you are on the Jira Cloud platform and you would like to be able to implement this process with Automation rules:

• https://jira.atlassian.com/browse/JSWCLOUD-19392

To set this up there are a few layers in the JQL filter, please refer to the following documentation as a referance point for the following filter:

• Searching for issues using Advanced Roadmaps details
• Advanced searching
  • Advanced searching - fields reference
  • Advanced searching - keywords reference
  • Advanced searching - development fields reference
  • Advanced searching - operators reference
  • Advanced searching - functions reference

In my Example I am using the following configuration, this my be different for you, noting i Set up  a dedicated project for the initiatives as covered in "Configuring initiatives and other hierarchy levels" for a multi project configuration:

• Two Projects configured
  • One for Epic and standard issue types, Issue Key ASDF
  • One for dedicated initiative issue types, Issue Key INIT
• Global Automation Rule
  • Set to the two affected projects
  • Will automatically Transition the initiative from To Do to Inprogress if a child Epic is set to in progress
  • The Branch Rule uses a Smart Value to look up the current issue and identify the Parent Initiative 

The filter can be set up to isolate the rule to Only issues in a single Plan OR to any issue in the project using one of the following Filters

Plan 1 Only:

"Parent Link" in issuesInPlan(1) AND issuetype = Epic

Any Plan affecting the issues incase the issues are split across multiple plans:

issuetype = Epic

Create a Global Automation Rule with:

• Trigger
  • When: Issue Transitioned
    • From ToDo
    • To In Progress
• Condition:
  • If: Issue Matches JQL
    • Either JQL noted Above 
• Branch Rule
  • For JQL:
    • issue in

    • parentissuesof("{{issue.key}}")

  • THEN: Transition Issue To
    • Copy From Trigger Issue

Using this automation, any time an Epic In project ASDF is transitioned to In Progress it will trigger the parent initiative to also be transitioned to the in Progress status.

Hope this helps.

Regards,
Earl