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

How can i have a sub task automatically inherit the assignee of the parent task or story? (Cloud)

Felix Ortiz

-I have been working in JIRA cloud for about a month.

-No programming experience.

-I am looking for options other than a add-on but i am still open to a add-on.

Accepted answers

somethingblue

Hi Felix,

I believe this is what you're looking for: How to Automatically Map Fields of a Parent Ticket to a New Sub-Task in JIRA Cloud. Although it does require JIRA Misc Workflow Extensions and once you've enabled it you would do the following:

Activate the add-on 'JIRA Misc Workflow Extensions' from https://<base-url>/plugins/servlet/upm/marketplace.
While editing the desired workflow, 'Add post function' to the 'Create' transition.
Select 'Set Field Value from Parent' and 'Add'.
Select the field to apply the transition.
Once complete, select 'Publish Draft' to ensure the workflow is applied to your project.

Hopefully this helps.

Cheers,

Branden

All comments

somethingblue

Hi Felix,

Activate the add-on 'JIRA Misc Workflow Extensions' from https://<base-url>/plugins/servlet/upm/marketplace.
While editing the desired workflow, 'Add post function' to the 'Create' transition.
Select 'Set Field Value from Parent' and 'Add'.
Select the field to apply the transition.
Once complete, select 'Publish Draft' to ensure the workflow is applied to your project.

Hopefully this helps.

Cheers,

Branden

Divya Yathagiri Venkata

Hi Branden,

I am trying to have the sub-task created with the same status as parent. I tried both of the below but the sub-task is still being created with 'New' status when I create one.

I tried to add the post-function 'Copy field value from parent issue (JMWE add-on)' [Set the value(s) of a field to the value of the same field in the parent issue] but this does not have Status field.

I have also tried to add a post function 'Copy Value From Other Field' to copy the status field from parent to sub-task which didn't work either.

How do I achieve this?

Thanks,

Divya

David Fischer

Hi Divya,

Jira, and especially Jira Cloud, will not let you set an issue's status. The only way to change an issue's status is through transitions.

Regards,

David

Divya Yathagiri Venkata

By transitions you mean manually moving the Sub-task to To Do, InProgress, Resolved etc? We are not on Cloud we are on JIRA server

Richard Herrada_hif9q3

You could use an automation rule to do this [Note that I did this for a single company managed project and have not rolled it out globally, but theoretically it should work globally too].

Go to project settings > hit automation > make sure your in the project you want to test the rule in > on the right hand of the screen click the blue create rule button.

From there your going to create the following:
[Trigger] When an issue is created,
[Condition] If the issue type is a sub-task,
[New Action] Then: Edit issue fields "Assignee" (in this one make sure to choose copy from parent)

Hit Save. Then publish the rule.

This won't update previously created sub-tasks, but it will work for newly created ones.

Good Luck!

Screen Shot 2022-01-14 at 6.43.48 PM.png

Ben Ernest-Jones

We started out there to solve this, with Automations, but now the new limits placed on Automations as of 1 Nov 2023 are so low that with just a couple hundred users Automations reach their monthly limits in about a week and they are now unusable for us.

Richard Herrada_hif9q3

I think I found another way around that. If your Epics, Standard Issue tickets (Tasks, Stories, etc.) and sub-tasks all use the same workflow, then I do not believe this will work / it may cause errors in other parts of your process.

However, if your sub-tasks have a unique workflow then you can set a "post function" when a ticket is "opened" to copy the assignee from the parent. Note 2 things:

Post Functions, currently, do not count against automation rules
The reason the sub-task needs to have its own workflow is because if you do not, then I think the tasks/stories will adopt the assignee of the Epic (which may not be a terrible thing, in some cases).

How you would do this:

Set up your workflow for the sub-task
In the Workflow between the dark circle and the "open" status there should be an arrow. Select that and on the right, select "post function" (see image)

Screenshot 2023-11-16 at 9.59.18 AM.png

On the Post Function screen, on the right, add a post function
Then select the post function option "Copy Value From Other Field" (see image) and at the bottom left, press "add"

Screenshot 2023-11-16 at 10.00.01 AM.png

Then select (see image):
- Assignee
- Assignee
- Copy from Parent
- Notes on this:
  - (Red Arrows) Because we are selecting "copy from parent" we want to find the assignee of the task/story, which is the source field.
  - (Blue Arrow) This is the field we want set.

Screenshot 2023-11-16 at 10.10.55 AM.png

Welcome!

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

Quick Links

Find more posts tagged with

jira