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; } } }

Use automation smart values for sub-task summary

Pauline Hild

Hi,

I've got a rule for creating subtasks automatically when creating a task that works very well but I want the name of the parent task be part of the summary of the subtask as well so that I can see to which parent task a subtask belongs to.

I tried several smart values but none of them worked.

This was the last one I tried:

Bildschirmfoto 2022-02-23 um 11.37.54.png

Does anybody know what I have to change within the smart values?

Accepted answers

Radek Dostál

Can you show us the whole automation rule setup so we can see how you have set it up? That way we can better know if the smart value here makes sense. Syntax-wise it seems fine so, curious what the rest of the setup is.

Bill Sheboy

Hi @Pauline Hild

There are known timing issues with the Issue Created trigger such that all of the information may not be available when the rule fires.

To know if this is the cause of what you are seeing...A work-around is to add a Re-fetch action immediately after your trigger. That will slow down the rule by reloading the issue data, and then it should be available for use.

Kind regards,
Bill

All comments

Radek Dostál

Pauline Hild

Yes, for sure. Here's a screenshot.

Bildschirmfoto 2022-02-23 um 15.40.39.png

Radek Dostál

Ah see, the trigger issue is the parent, "Then: Create a new issue" and "Then: Edit issue" - those are 2 separate actions, and it is trying to modify the trigger issue - not the subtask. So because the trigger issue cannot have a parent, the action does nothing.

Can you try to specify the summary in the 'Then: Create a new' action like so (I hope Cloud automation has it as well, I tried with on-premise so..):

((Note I changed it to '{{triggerIssue.summary}} Task'))

Pauline Hild

Okay, now I understand the problem. I changed it the way you did in my rule but it doesn't work yet. Is there anything wrong?

Bildschirmfoto 2022-02-23 um 16.11.16.png

Bill Sheboy

Hi @Pauline Hild

There are known timing issues with the Issue Created trigger such that all of the information may not be available when the rule fires.

Kind regards,
Bill

Pauline Hild

Hi @Bill Sheboy

Thank you very much for your answer. I tried to add a Re-fetch action after the trigger but unfortunately it still doesn't work. Now I'm completely at a loss what else I could try. However, I'm very grateful for your help.

Kind regards,

Pauline

Bill Sheboy

That is curious...just to confirm the conditions, would please post images of:

your current rule that does not work as expected,
the rule details section showing the settings, and
the audit log details for the execution?

And, are you using Jira Cloud or Jira Server/Data Center version?

Thanks!

Pauline Hild

I'm using Jira Cloud.

Note 1: The first screenshot doesn't show the hole rule but there are only more "Then: Create a new Sub-task" components so nothing different

Note 2: I already tried to add the "Re-fetch" in several positions but none of them worked

Bildschirmfoto 2022-02-25 um 09.03.33.png

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software