Jira automation: adding a prefix to tasks, based on their related story

[ori gal]

Hey everyone,

I'm using Jira Stories to contain the product user stories written by the PO, and for each story, we open R&D tasks. the connection between them is "relates to".

I would like that each task will have a prefix with the Story name.

Example: 

Story: Cancel Case Offer

Related task: [Cancel Case Offer] Cancel case offer details when changed on SF

3 questions:

1. any idea how to automate this?

2. The trigger IMO should be the association between the story to the task. any thoughts about this?

3. Are you familiar with good ways to visualize the relationship between stories and related tasks in day-to-day work?

Thank you!

[John Funk · Accepted solution]

Hi @ori gal 

Are you using an Automation Rule to create the R&D tasks and link them to Story? If not, how are you creating the tasks? 

[ori gal]

Hi John,

We are creating the tasks manually. In some cases, the developers open the tasks directly from the Story ticket, and in other cases, they are linking them to the story afterward.

[John Funk]

If you create them manually, and then link them manually, you can have an automation trigger fire that will will update the Summary of the newly created issue based on the one it is linked to. 

[ori gal]

And what if I prefer to have it done on the ticket name as a pre-fix? is that possible?

[John Funk]

That's what I would do. I would add a manual automation rule that you can execute from the Story that creates the Tasks and links them. Then you can copy down the summary from the related Story to the Tasks. 

[ori gal]

ok, I confused Summary and Description. my bad. thank you very much!

[ori gal]

I understand how the trigger will work, however, I'm having trouble fetching the related issue summary and using it as the prefix.

What am I doing wrong here?

[ori gal]

@John Funk 

[John Funk]

Not sure you are going to be able to do it that way since it might not be the other issue that is the trigger issue. 

Maybe try adding a Branch to capture the linked issue before doing the Edit issue action. You would need to change the triggerIssue part as well. 

[ori gal]

Hi @John Funk ,

The trigger is working fine and the Summary is updating, only I cant manage to fetch the related issue Summary that I want to populate as a prefix in the task Summary. 

[John Funk]

That’s what I’m saying 😊

Did you try my suggestion?

[ori gal]

Hi @John Funk  and thank you for the prompt response.

I tried but not successfully. 

Any chance you can show me how to do this?

"Maybe try adding a Branch to capture the linked issue before doing the Edit issue action. You would need to change the triggerIssue part as well. "

[John Funk]

Can you share what you tried? And what didn't work with it?

[ori gal]

[John Funk]

Let's try this in the summary: 

{{destinationissue.summary}} – {{issue.summary}}

[ori gal]

It's changing the Summary of the Parent instead of the child

[John Funk]

Okay, let's go back to your original setup by removing the Branch. Move the edit up first before deleting the branch so you don't delete that too. Then try again. 

[ori gal]

it worked! thank very very much @John Funk !

[John Funk]

Sorry, I should have thought of that the first time. Glad it worked!