nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Push/update field data from subtask to task

Quinn Campbell

I have a subtasks that requires a user to fill in a data field with a value. What is the best methodology to have that data push up from the subtask to fill in that field at the task level?

During the process of an issues life it gets more and more subtasks assigned as it transitions through the workflow fields. Only some of those tasks requiring filling that data field. While not entirely necessary it would be nice if that task level field was updated instantaneously but would be acceptable if it updated on a transition rule i.e only got updated once it transitioned to the next stage in the work flow. Whats the best way to do this?

Accepted answers

Bill Sheboy

Hi @Quinn Campbell

You could do that triggered on either (or both) the subtask create or issue field update. Or on the issue transition if that is the point at which your required field needs to be filled.

However...when there are multiple subtasks for an issue, how will you know which one should be used to update the parent issue?

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Quinn Campbell

You could do that triggered on either (or both) the subtask create or issue field update. Or on the issue transition if that is the point at which your required field needs to be filled.

However...when there are multiple subtasks for an issue, how will you know which one should be used to update the parent issue?

Kind regards,
Bill

Quinn Campbell

I'm a bit lost as to what youre saying/asking? So would I need to create an entirely new automation that is triggered on issue field update/subtask create?

To your second point, would I need to create a new rule for each field that gets updated?

Bill Sheboy

My apologies if I was unclear; I will try to clarify...

In general, to copy a field value from the subtask to the parent issue, you would need 2-3 rules:

triggered on issue create, checking if the issue is a subtask, and then editing the parent
triggered on an update of your field, again checking if the issue is a subtask...
[edge case] if you move subtasks from one parent to another, this rule would trigger on a change to the parent issue, and then perform the other steps. The extra part is deciding what to do with the previous parent's fields.

I thought you originally noted only syncing one field, but if there are several fields the options are: sync all the fields with on rule, or create separate rules for the update of the field case, one for each field

The part I am still unclear on: if there are multiple subtasks for an issue, each with a different value in your field-to-sync, which one should be used to update the parent? Is there some criteria to decide? For example:

Parent story ABC-123
- subtask ABC-456, with field value of "apple"
- subtask ABC-789, with field value of "orange"

What value should be used to update the parent, ABC-123?

Quinn Campbell

yeah I understand your second question, I think the only way is to make a standalone rule that has all the fields that get filled out, and when they are filled out to trigger an update to their parent.