When a subtask is created, it inherits the value from a custom field 'Customer' on the parent task via a Post Function 'The value(s) of field Customer will be set from the issue's parent (replacing existing value). This works great!
Later, we found out the parent task was incorrect and we changed the parent value to a different customer but the customer field on the subtasks did not change. This is not good!
How do I get around this?
That's correct behaviour - subtasks are issues in their own right, and although grabbing a default from the parent is quite handy when they're created, the fields belong to the subtask, they're not tied to the parent.
You'll need a listener that can catch "parent updated" and run some code to iterate over the sub-tasks and update the values. I don't think there is one of these available for Cloud though.
(This is a weakness in JIRA in my opinion - there should be a way to flag subtask fields as directly inherited from the parent so that they appear, read only, on the sub-tasks, so you can search and sort on them, see them when looking only at the subtasks, and you don't have to think about maintaining them)
A couple of options:
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs