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

Update custom field of bug based on Epic status

dimofeev

Hi there,

I would like to achieve the following automation:

1. Create read-only field for Bug and Story called 'Phase'.

2. When the Parent field of any Bug or Story is updated (for example create Bug or Story in Epic) get the status of the Epic and set it for the 'Phase' field.

My end goal is: We have different statuses for the Epic - Development, Alpha, Beta, etc. and we would like to track how many bugs / stories are discovered during different Epic statuses.

Thank you in advance for your help.

Accepted answers

Bill Sheboy

Hi @dimofeev -- Welcome to the Atlassian Community!

What have you tried thus far to solve this need?

If you have a rule and it is not working as expected, note context is important for the community to help. Please post the following:

what version of Jira are you using: Cloud, Server, or Data Center
for Cloud, what type of project is this (e.g., company-managed, team-managed, etc.)
an image of your complete automation rule in a single image for continuity
images of any relevant actions / conditions / branches
an image of the audit log details showing the rule execution
explain what is not working as expected and why you believe that to be the case.

If you have not tried creating the rule yet, I encourage you to do so. Successfully using automation rules requires learning and experimentation.

To help you get started, the rule could be triggered on Issue Created, and then access the parent Epic's status to edit the Bug or Story's field. Please look here to learn more: https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

Kind regards,
Bill

All comments

Bill Sheboy

Hi @dimofeev -- Welcome to the Atlassian Community!

What have you tried thus far to solve this need?

If you have a rule and it is not working as expected, note context is important for the community to help. Please post the following:

what version of Jira are you using: Cloud, Server, or Data Center
for Cloud, what type of project is this (e.g., company-managed, team-managed, etc.)
an image of your complete automation rule in a single image for continuity
images of any relevant actions / conditions / branches
an image of the audit log details showing the rule execution
explain what is not working as expected and why you believe that to be the case.

If you have not tried creating the rule yet, I encourage you to do so. Successfully using automation rules requires learning and experimentation.

Kind regards,
Bill

dimofeev

Hey Bill,

Thanks for your prompt reply. We are using Cloud Jira Software.

What my final automation goal is the following:

1. I have Product Discovery Project with Ideas in it. These Ideas have standard status field (Parking Lot, Delivery, etc.)

2. For every Idea from that project I have one Epic attached. The epic is part from other project that is Company-managed software.

3. For every epic I have many stories (and potentially bugs).

Now, I want to create new custom text field that should be available for the Stories and Bugs. When a Bug/Story is created and related to the Epic, the custom field should be populated with the status of the Idea (i.e. not with the status of the Epic).

Do you think this is doable? Thank you in advance for your help.

Bill Sheboy

While that is possible with an automation rule, it seems problematic for several reasons:

First, it is going from the lowest issue item --> upwards to gather and display the Idea status, which seems the opposite of what many would use to assess progress. What problem are you trying to solve by showing the Idea status in those issues used to implement it?

Next, although the Idea status is likely changing less often than the Stories, when it does it could potentially update many items. That will create a very slow rule, and potentially one that cannot finish if there are more than 100 issues involved (due to rule limitations).

I recommend pausing to meet with your Jira Site Admin, explain the problem you are trying to solve (that is, "why do this?"), and collaborating on possible solutions.

dimofeev

Thanks, Bill,

I would like to know how many bugs/stories are logged during the different Idea statuses (not done, discovery, development, alpha, beta, etc.). That way we can see how effective we are during the different release cycles of given feature.

The idea is to create one custom field, let's say 'Phase' add it to Bugs/Stories and fill it only once (i.e. no subsequent updates of this field) with the status of the Idea.

So finally it will looks like.

1. I have Idea and log it in the Jira Product Discovery project. It has some status (let's say 'Discovery').

2. New Epics (deliverables) are created and linked to this Idea.(Epics available under Delivery section of the Idea and resides in Company managed Jira project).

3. Now when I create new Bug or Story and it is linked to some of these epics, a custom field available for Bugs and Stories should be populated with the status of the Idea. This field should be populated only once and no subsequent updates of it. If you change the status of the Idea (or Epic) - this custom field should not be updated.