Hey folks, I’m having trouble with my Jira subtask template (version 7.13.5). I want the Subtask Summary to include the Task Summary, but it’s not working.
I’ve tried these two formats:
Rack: "@inherit" / description:"Rack procedure for devices" / assignee:jiradatacenter / cfield:"Customer:@inherit" / duedate:"@inherit" / priority: "@inherit" / labels: "Datacenter"
Rack: @inherit / description:"Rack procedure for devices" / assignee:jiradatacenter / cfield:"Customer:@inherit" / duedate:"@inherit" / priority: "@inherit" / labels: "Datacenter"
The other @inherit fields are pulling data correctly, but the Summary won’t budge. Is this a version thing? Anyone else run into this?
I’ve encountered a similar issue in Jira 7.x versions. The @inherit functionality for Summary fields in subtask templates was indeed problematic in earlier versions. Have you considered upgrading to a more recent Jira version? In my experience, this particular inheritance issue was resolved in later releases.
Alternatively, you might want to explore using the ‘Clone’ feature instead of subtask templates. While not as automated, it does carry over the Summary field content, which you can then modify as needed. It’s a workable solution until you can upgrade or if upgrading isn’t feasible in your current setup.
Lastly, double-check your project’s configurations and custom field settings. Sometimes, unexpected interactions between custom fields and inheritance can cause such behaviors.
As someone who’s been wrestling with Jira for years, I can tell you that version 7.13.5 is notorious for quirks like this. The @inherit function for Summary fields in subtask templates was a bit of a mess back then.
I ran into this exact problem and found a workaround. Instead of relying on @inherit for the Summary, I started using Jira’s built-in variable substitution. Try something like this in your template:
Summary: ${parent.summary} - Rack
This pulls the parent task’s summary and adds ‘- Rack’ at the end. It’s not perfect, but it gets the job done until you can upgrade.
Speaking of which, if you have the option, I’d strongly recommend upgrading to a newer Jira version. They’ve ironed out a lot of these inheritance issues in more recent releases. It’s a bit of a pain to upgrade, but it’ll save you headaches in the long run.
yo alex, i feel ur pain. jira 7.x was a nightmare with this stuff. have u tried using a script runner? it can do some magic with field inheritance. also, check ur project settings - sometimes theres weird permission stuff blocking inheritance. if all else fails, maybe its time to bug ur admin about upgrading lol. good luck man!