Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Automation for Jira Smart Values in Sub-Task Summary

I have an Automation for Jira rule set up to create sub-tasks for a specific type of issue. I would like to include the name of the epic and parent task in the name of the sub-task so that the person it is assigned to know what they are working on at a a glance. For example, if there is an epic "Website" with a task "Home Page" and a sub-task "Wireframe" that is assigned to a designer, I want the summary of the sub-task to be "Website Home Page Wireframe." I have tried the following in the summary field:

  • {{issue.parent.epic.summary}} {{issue.parent.summary}} Task
  • {{parent.epic.summary}} {{parent.summary}} Task

In both cases the summary is just set to "Task."  Is it not possible to use smart values in the summary or am I referencing the wrong values?

3 answers

1 accepted

2 votes
Answer accepted

Hello Blair,

The smart values you used on your Automation rule has properly worked for me - It properly added the Epic and Story summaries to the sub-task. Here's the rule I executed:

Screen Shot 2019-01-15 at 18.12.21.png

That being said, I believe that something might be blocking your Automation rule. Please, check the Audit Log of your automation and check if it returns any errors.

Additionally, if the Epics and Stories are on different projects, make sure you configured your rule globally to work cross projects.

We will be waiting for your answer.

Thank you for this! Originally I was trying to set the summary in the same step as creating the sub-task, but having a separate rule also works for what I need.

Like # people like this

You are welcome, Blair!

Have a nice day!

Like Jurica Petricevic likes this

@Blair Chisholm I have the same desire to auto-create sub-task after I had created a story. I found the reason why it doesn't work if we put in 1 automation rule

While creating the subtask into the parent issue, Jira cannot get this param {{issue.parent.summary}} Jira can only work once the subtask is created.

Was having the same trouble and I manage to solve it using a "Re-fetch issue data" before the subtasks creation. That way it can get the right parent summary adding some info to distinguished both.

 

In my case when a TASK is created, JIRA creates 2 subtasks automatically, called TASK_1 and TASK_2 

Like Alexey Paveliev likes this

If you want to create an Issue (i.e. Enhancement) with automated subtask creation where the subtask's summary includes the parent's summary, you will have to first create the issue, then create the subtask and rename it separatly. It seems Jira canoot do it in the creation process.

 

2019-05-31_11-09-27.jpg 

In this example, for an enhancement in this projet, a new subtask "Conduct Meeting" will created with "Meeting" as summary. Then this subtask will have its sumary renamed to "Meeting: {{issue.parent.summary}}".

I suggest you add a condition to make sure you are not renaming another subtask that may be present when creating several ones in the same project automation.

Thank you, that was the trick.


How can i make this work for JIRA next gen project. I would like to append the Epic name to the Tasks under. Tried using the same smart values as above and it doesnt work. Please help. Thanks.

I have the same request.  Append the Epic name as part of the Issue creation process.  Anyone have some ideas for next gen project?

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

302 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you