nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Links between sequential stories - Jira Automation

Herick Carvalho

Olá a todos!!

Tenho um projeto automatizado que a partir da criação do Epic, gera varias historias e subtarefas dentro de cada historia. Cada historia criada vai ser bloqueada pela anterior, como segue na captura.

Pela quantidade imersa de subtarefas a serem criadas, dividi as historias em regras individuais com gatilhos sequenciais. Quando configuro a historia para ser associada a ultima criada ela, não funciona e não aparece nenhum vinculo.

Alguem poderia ter uma ideia do porque nao consigo vincular uma historia a ultima criada? Como seria a forma ideal de realizar essa demanda ??

Qualquer ajuda será apreciada.

Obrigado!!

----------------------------------------------------------------------

Hello everybody!!

I have an automated project that, after creating Epic, generates several stories and subtasks within each story. Each story created will be blocked by the previous one, as follows in the capture.

/* first screenshot */

Due to the large number of subtasks to be created, I divided the stories into individual rules with sequential triggers. When I configure the story to be associated with the last one created, it doesn't work and no link appears.

Could anyone have an idea why I can't link a story to the last one created? What would be the ideal way to fulfill this demand??

Any help will be appreciated.

Thank you!!

Accepted answers

Bill Sheboy

Hi @Herick Carvalho -- Welcome to the Atlassian Community!

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!

Until we see those...

You describe splitting the issue creation across different rules. As a result, the different rules do not have context / scope to access the other issues for linking. If you can find the issues with JQL, you could use the Lookup Issues action to identify their keys to support the linking...although your rule timing of when the issues are created may make that difficult.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Herick Carvalho -- Welcome to the Atlassian Community!

Until we see those...

Kind regards,
Bill

Herick Carvalho

Hi @Bill Sheboy -- Thanks for the answer and sorry for the vague question.

Below is a capture of the pattern of my branching rule, where it is activated by the previous trigger and in sequence a history is created with its configurations and subtasks, and finally the summary trigger is created for the creation and execution of the next rule.

My attempts to create a sequential link between stories are as follows:

Attempt 1: I configured it within the story itself through the "Associated Items" field. The rule followed successfully but no link was created. I also tried to place an action to edit associated items in the story creation sequence and got the same result.

Attempt 2: I created a branch for "Last item created" and a link was created with the main Epic, as follows in sequence.

Attempt 3: I added the edit link action within the subtasks branch and a link was created between all subtasks.

I hope I explained my problem and my attempts and results more clearly.

Bill Sheboy

One challenge with linking created issues in rules is context: the definition of "most recently created issue" changes as issues are created, including more challenges if branches are used.

To do what you describe, you may need to either save the issue keys in variables or use separate rules to add the subtasks.

For a basic rule to add a series of linked stories, a rule would be this:

trigger: some trigger
action: create issue A
action: create issue B, adding a link to "most recently created issue"
action: create issue C, adding a link to "most recently created issue"

But to do that with sub-task creation also, the keys must be saved first.

trigger: some trigger
action: create issue A
action: create a variable to save {{createdIssue.key}} as varKeyA
branch: to most recently created issue
- action: create subtasks for issue A
action: create issue B, adding a link to {{varKeyA}}
action: create a variable to save {{createdIssue.key}} as varKeyB
branch: to most recently created issue
- action: create subtasks for issue B
action: create issue C, adding a link to {{varKeyB}}
branch: to most recently created issue
- action: create subtasks for issue C

Herick Carvalho

Thanks @Bill Sheboy--- It explained a lot to me about my problem. But I still have a doubt.

In my case, the stories are created in a rule individually. To use the story key in another rule (Rule I created the variable {{varKeyA}} and commented it in Epic and after triggering the next story I used {{issue.comments.first.body}} to define it. it as {{varKeyA}} in rule B and so I can theoretically use the variable from rule A in rule B.

Rule A

Rule B

To follow the plan you described, you need to create problem B by adding a link to {{varKeyA}}. That part was beyond my knowledge. Could you help me with how I could add varKeyA as a binding object? Since the Blocked By field only shows "Last item created" and "Trigger item"

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation