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; } } }

Populate a field from child tickets

Christopher Atkinson_31x504

Hi all,

I'm wondering if anyone out there has any advice or a solution to the following:

I want to run a report of how many "Initiatives" Teams are involved in and spot when they are overloaded in a more instantly visual way that I can see to do in Jira/ Advanced Plans.

I am trying to work out how to populate a field in a parent ticket by copying values from the children ticket.

Eg:

Parent Ticket - Field: "Teams Involved" - Value: "Team A" "Team B"

Child Ticket A- Field: "Team" - Value: "Team A"

Child Ticket B- Field: "Team" - Value: "Team B"

The automation has also got to cope with:

- Tickets from the same team being added and not trying to duplicate the current Team Value,

- Some Tickets being removed but not removing the Team from the Parent if some are still linked,

Thanks in advance!

Accepted answers

Ste Wright

Hi @Christopher Atkinson

Can I confirm the logic here...

The Parent will have a field - eg. Select List (multiple choices) with all Teams in it
The Children will use the standard Team field
Each Team should be displayed just once at the Parent level
If an issue is removed and no other issues have that Team, remove them from the Parent

...is this correct?

Ste

All comments

Trudy P Claspill

Hello @Christopher Atkinson

You might want to use a Labels custom field in your parent issue.

You could create a scheduled rule that gets a list of the parents that you want to update.

Then for each parent you would

- clear the custom Labels field

- walk through the child issues

- pull the Team value from each child and add it to the custom Labels field of the parent.

If the Team value is already present in the custom Labels field, it won't be added again.

Another alternative that might work would be a rule triggered by a change to the Team field of a child issue. I haven't worked out the details on that rule.

Ste Wright

Hi @Christopher Atkinson

Can I confirm the logic here...

The Parent will have a field - eg. Select List (multiple choices) with all Teams in it
The Children will use the standard Team field
Each Team should be displayed just once at the Parent level
If an issue is removed and no other issues have that Team, remove them from the Parent

...is this correct?

Ste

Christopher Atkinson_31x504

Yes, that look about right

Ste Wright

Hi @Christopher Atkinson

Rule is below. Please see the notes for some additional information.

---

Prerequisites:

Get the custom field ID for Team in your instance - eg. 10001
Create a Select List (multiple choices) at Epic (or parent) level, eg. All Teams. Populate with all available Team options.

---

(1) Trigger: Field Value Changed
- Field to monitor = Team
- Change type = Any changes to the field value
- For = All issue operations
(2) Condition: Issue Fields Condition
- Field = Issue Type
- Condition = is one of
- Value = Task, Story
(3) Condition: Related Issues Condition
- Related issues = Parent
- Condition = Exists
(4) Action: Lookup issues
- JQL - parent = {{triggerissue.parent}}
(5) Action: Create variable
- Name = TeamList
- Smart value = {{#lookupIssues}}{{#customfield_10001}}{{name}}; {{/}}{{/}}
(6) Action: Create variable
- Name = AllTeams
- Smart value = {{TeamList.split("; ").distinct.join(",")}}
(7) Branch: Related Issues
- Type = Parent
  - (8) Branch-Action: Edit Issue
  - More options...
    - {
      "fields": {
      "All Teams": [
      {{#AllTeams.split(",")}}{"value":"{{.}}"}{{^last}},{{/}}{{/}}
      ]
      }
      }

---

Notes:

(1), the Trigger, could be multiple events - including a Team being added or removed to an existing child, a new child being added, a child being removed, etc. You could either...
- Have multiple rules, with different Triggers - I think you'd need at least two...
  - Field Value Changed = Parent
  - Field Value Changed = Team
- Run this rule on a Schedule, to avoid unnecessary triggers and executions
(2) can be limited to whichever issue types are relevant as children of the parent.
(5) is where the Team custom field ID is used
(8) updates the Select List (multiple choices) at the parent level. The values in here need to match all Team options available (based on the names) for this to work.

---

Give this a go, and let us know if it works for you

Ste

Christopher Atkinson_31x504

Hi @Ste Wright ,

Thanks for the suggestion above!

I've put it in place and the audit log is saying that I have success.... BUT I don't see any of the Team Names appearing as selected. Any ideas?

I've checked that the list matches the names of the teams...

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud