I’m working with Jira and need help with subtask naming. In my project setup, I have a custom field called “Definition of Done” that contains 5 standard tasks that must be completed before closing any ticket. When I convert these tasks into subtasks, I want them to automatically get named using a specific format that includes both the parent ticket name and the task description.
For instance, if my main ticket is titled “Mobile App Redesign” and I create a subtask from a task called “Button Styling Fix”, I want the resulting subtask to be automatically named Mobile App Redesign / Button Styling Fix.
Is there a way to configure Jira to handle this automatic naming convention? Any suggestions or workarounds would be greatly appreciated.
I’ve dealt with this exact situation on complex feature tickets. The automation works, but I’d add a branch condition to check if the subtask summary already has the parent title - prevents duplicates when editing existing subtasks. Also throw in a character limit check since those combined titles can get crazy long in the UI. I tweaked the smart value format with some conditional logic for cases where the parent summary might be null or empty. Tested it across different issue types and it’s been rock solid.
i did this with a cloud automation rule in jira. set it to trigger on issue creation, add a condition for subtasks, then use ‘edit issue’ to change the summary to ‘{{issue.parent.summary}} / {{issue.summary}}’. works well, but adjust the format if titles are too long.
You can’t do this with standard Jira, but I’ve handled similar requests using automation rules. Set up a rule that triggers when you create a subtask - it’ll update the summary by combining the parent issue’s summary with the subtask title. Use smart values like {{issue.parent.summary}} to add to the existing subtask name. Just watch the timing so you don’t lose the original name. You could also try a post-function in a workflow transition for better control over renaming. If you’ve got ScriptRunner, that’s your best bet for a custom solution that handles edge cases better.