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

Copy field from parent to sub-task

GilK

Hi,

I have an issue type named: release and it has sub-task of type sub-bug.

I want the component of the release to be filled automatically in the Create Issue screen of the sub-bug, with the same component of the parent (release) issue.

Also, I want the Fix version of the release (the parent) to be copied as the Affected Version of the sub-bug (the sub-task) automatically, prefebely filled in the Create Issue screen (but not a MUST).

Thanks,

Accepted answers

Natalie Hobson

I highly recommend JIRA Misc Worklfow Extensions:

https://marketplace.atlassian.com/plugins/com.innovalog.jmwe.jira-misc-workflow-extensions

It has post functions that allow you to set field value from parent (any field). I use it in my workflows and it does the job. It also has other quite useful workflow additions.

All comments

Dieter

If it's ok for you to create the subtask in a transition, Bob has the solution for you at https://bobswift.atlassian.net/wiki/display/CSOT/JIRA+Create+on+Transition+Plugin#JIRACreateonTransitionPlugin-Description Please give this a try, it's really powerful since the latest versions

Ramiro P

I'll recommend too a solution in case that you want to create the subtask on a transition. I'm doing something like that, but with two standart issue types and a issue link with the most famous Script Runner plugin. But I'm sure you already have that...

GilK

Hi,

I create the sub-bug (of Sub-Task) type manually, when we find a bug.

Therefore I cannot use the "Create subtask in a transition" solution, or I don't understand you correctly.

The best solution would be to fill the parameters in the Sub-Task Create screen.

Thanks,

Janiv.

GilK

See my previous comment,

Thanks,

Janiv.

Dieter

Yes, i understand that. You would need to train your users to use a workflow action instead an operation. what might help would be to disable the original operation, put the workflow action at the very beginning and make it a global action that is available in all steps. Ok, said that , i see this is a lot of effort so Ramiros suggestion seems much better. it would just require to add a groovy post function to the create transition of the sub-task workflow

Natalie Hobson

I highly recommend JIRA Misc Worklfow Extensions:

https://marketplace.atlassian.com/plugins/com.innovalog.jmwe.jira-misc-workflow-extensions

It has post functions that allow you to set field value from parent (any field). I use it in my workflows and it does the job. It also has other quite useful workflow additions.

andreas_qezsu8

There's now a very easy to configure way to keep fields for parents and sub-tasks in sync using Automation for JIRA!

You can easily modify related issues (such as parents, stories, sub-tasks, epics, linked issues and even JQL) using our related issues action and condition:

edit-sub-tasks.png

(this example updates the description, but pretty much any field can be edited)

For more details see https://blog.codebarrel.io/synchronize-parent-and-sub-task-issues-with-automation-for-jira-bdcca6c9d453

edit-sub-tasks.png

Lukas Gotter

Another valid option is the "copy value from parent to sub task" post function of Workflow Essentials for JIRA. Its not free but has a lot of functionality to create custom workflows without any programming.

LECOQUIERRE Hugues

Hi there!

I have the same issue....

Any solution that is not sponsored by a paid app?

Thanks!

Ory Zaidenvorm

It may be easy, but very expensive for cloud instances of JIRA!

Balavinayagamoorthi

If you are interested to apply the settings in Global level "Copy to Subtask Plugin" is very helpful. Free but unsupported plugin.

Carrie Hunt_e2yx66

This of course still seems only in the case of using it within your workflow and not doing bulk edit of fields that already exist in sub-task tickets that have already been created and now need to copy their parent data fields down without a workflow.

Michael Rother

For the record: "Copy to Subtask Plugin" can't handle Lables, since they aren't a "custom" field.

Sayan Kaiser

There is no use-case

Welcome!

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

Quick Links

Find more posts tagged with

jira

transition

sub-task