Automation - Transitioning Issues only moves the Epic but not the Tasks

[Kevin Drescher]

Hello,

I think the question is clear, screenshot for details:

I dont know why but the epics get transitioned correctly and the tasks stay in backlog...

[Bill Sheboy · Accepted solution]

Hi @Kevin Drescher 

This symptom is caused by branch scoping: you are branching to the created epic so you can add the child Tasks, and later outside of the branch the newly created Tasks are not "visible" as created.

One possible fix for this is to remove the first branch, like below.

• trigger: scheduled
• action: create issue for your Epic
• action: create variable (to save the epic key)
  • variable name: varEpicKey
  • smart value: {{createdIssue.key}}
• action: create issue for your Task, and...
  • set the Epic Link to {{varEpicKey}}
  • To use a smart value for this field, type or paste in the smart value, and it will appear below the field.  When it does, select it to use as the field source.
• action: create more tasks...
• branch: on created issues
  • action: assign the issue
  • action transition the issue

Kind regards,
Bill

A follow-up: I find this behavior/symptom quite surprising, as branches on one-and-only-one-issue are described by Atlassian as run in-line, as if there was no branch, while multi-issue branches run in parallel and asynchronously.  Seems that guidance has some variation to it  :^)

[Kevin Drescher]

Hey,

It kind of works, but somehow doesnt recognize the second epic. 

The second variable tries to use the first created task instead of the epic just created before.

Like this

- Epic (Main 73)

---- Create Variable of most recent Issue = Main 73

-- Task (Main 74)

-- Task (Main 75)

-- Task (Main 76)

- Epic (Main 77)

---- Create Variable of most recent Issue = Main 74 ????

-- Task (Main 78)

-- Task (Main 79)

-- Task (Main 80)

---- Assign all Issues

---- Transition all Issues

What is going on here?

[Bill Sheboy]

Hi, Kevin.

Sorry, as I did not see in your rule you were creating multiple epics, with associated tasks. 

If you are trying to do this repeatedly (e.g., add an epic, add tasks, and link to that epic), you will need to repeat the pattern I suggested AND use a different created variable as a precaution.  Something like this:

• ...
• create the epic
• save the key in a variable (e.g., varFirstEpicKey) with {{createdIssue.key}}
• add the tasks, linking to {{varFirstEpicKey}}
• ...

• create another epic
• save the key in a variable (e.g., varSecondEpicKey) with {{createdIssue.key}}
• add the tasks, linking to {{varSecondEpicKey}}
• ...

If instead I am missing something, please add an image of your complete rule, perhaps using a browser, scrolling image capture tool.

[Kevin Drescher]

Can you make a screenshot of the 

• save the key in a variable (e.g., varFirstEpicKey) with {{createdIssue.key}}

part?

I thought that thats what I am doing already by logging {{createdissues.get(1).key}}?

[Bill Sheboy]

This is what I described earlier: first create an epic and then reference only that epic using {{createdIssue}} (note this is singular) and not the list of issues.

As you seem to be changing the scenario you originally asked (by adding more epics) I ask that you post an image of the complete rule in one continuous image.  Seeing the entire rule at one time will provide context to answer your questions.  (You can use a screen grab tool or browser addon to do this.)

[Kevin Drescher]

Thanks, it worked. I used the "log" function and not the "create variable" function.

[Bill Sheboy]

Great!  So is the rule working as expected now?

[Kevin Drescher]

Yes it does, thank you

[Najm Polaris]

@Kevin Drescher ,

Add a transition step right after the task is created. 

[Kian Stack Mumo Systems]

@Kevin Drescher, 

Is there a transition from the initial status -> ROCKANDSTARS?

Thanks,

Kian

[Kevin Drescher]

Hey,

yes, the created issues (both epic and task) do not get a status when created and per default land in backlog. I then want to transition all of them to "rockandstars", which works, but only for epics somehow.

The tasks are successfully linked to the corresponding epics but they stay in backlog.