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

subtask to inherit data field from parent issue/story

Jacob A. Albrektsen

Is it possible for a subtask, to inherit a datafield from a parent issue. We have some stories, which we assign to a given patch “Fix Versions” in jira. But as for now we need to assign the underlying tasks for “fix versions” and we need it to happen automatically. Is this possible?

Accepted answers

All comments

Tessa Tuteleers

Hi @Jacob A. Albrektsen ,

you do this in 2 different ways:

(easiest but needs admin access and will only happen on the specified transition) Use the "Copy value from other field" postfunction in your workflow for the subtask
Or use an automation rule to get the value from the parent and copy to all its subtasks.
You might need to set multiple triggers
- Issue created -> if a subtask is created, get the value from the parent
- "issue updated" -> if the parent is updated, copy the value to all the subtasks

Hope this helps!

- Tessa

Jacob A. Albrektsen

Thank you @Piet Pieters

I will try this later, actually this is a little tricky, as I am not admin in this project, and it is a project that collects data from multiple projects from all of our value streams

Tessa Tuteleers

Sub-tasks are always in the same project as their parent, so as long as the scope is limited to that project, the project admin should be able to do it.

Best check in with them or the jira admins.

Best of luck!

- Tessa

Jacob A. Albrektsen

@Piet Pieters Got it to work on newly created issues, I need to find out of how to bulk update the old ones

Fabian Kiesewetter

Hey all,

I'm struggling with the last piece here. I got subtasks to follow their parent tickets for newly created issues, but not for edits after their creation. My approach would be:

Trigger: "issue is updated"
Condition: "Subtasks do exist" (probably not necessary)
Action: "Copy field XY from parent to subtask"

The last step here seems to be the problem as there is only "copy from parent" and not "copy to subtask". Since the trigger should be the parent issue I can't seem to make this work without the right action here.

@Piet Pieters Any advice?

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-software

jira-software-cloud

atl-gruland