Is there a smart value to inherit parent name?

Question

Hello Community!
I am trying to elaborate on the automation where the subtasks of the story are created with specified fields in them.
one of the subtasks is DEV, other is DESIGN.
What interests me - is there a smart value, that, when added to the summary field I specify for the subtasks, will allow them to inherit the Summary of the Story AND. either DEV or DESIGN along with it?

Bill Sheboy · Answer

Hi!  I recommend moving the Re-fetch up to immediately after the trigger.  Otherwise there is a chance that JQL condition could fail to match when the data is not ready yet.

Dave Armstrong_erd7cf · Answer

Thanks @Bill Sheboy that got it working. I assume only the original poster can "accept" an answer, but I truly appreciate your help.

I already had a branch under the "When: Issue created", so I just had to add the "Re-fetch issue date" action and then I updated my "Create a new Sub-task" to include {{issue.summary}} in the Summary, worked like a charm.

My rule now looks like this:

* When: Issue created
* (Branch rule) For Current issue* (New Condition) If: Issue matches JQL
* (Action) Then: Re-fetch issue data
* (Action) And: Create a new* Project = Same project
* Issue type = Sub-task
* Parent issue = Current issue
* Summary = {{issue.summary}} - Development Phase

Bill Sheboy · Answer

Hi @Dave Armstrong

If you remove your branch to Current Issue, you may then reference the trigger issue's summary when the subtask is created with either of these:

Also of note: the Issue Created trigger and fire faster than the data is available to a rule, leading to problems.  The work-around for that is to add a Re-fetch Issue action immediately after the trigger; this will slow down the rule and reload the data before proceeding.

If that does not help, please post images of your complete rule and the audit log details for context.

Kind regards,
Bill