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

JIRA Automation: Set all issue to type bug for just 1 epic in a project

Mahesh Swaminathan

I'm trying to Set all issues to type bug for just 1 epic (parent) (ex: MPP-3100) in a project when a parent field changes.

The automation seems to pass for all values of parent value even ones that aren't the value set in JQL (have the same issue if I use smart value {{issue.parent.key}}

Any help? Thanks

Screen Shot.png

Accepted answers

Fabian Lim

Hi @Mahesh Swaminathan

In order to change issue types they have to have the same workflow. Maybe that's why it's not working. Details: https://community.atlassian.com/t5/Jira-Service-Management/Automation-and-change-issue-type/qaq-p/1324075

Regards,

Fabian

All comments

Fabian Lim

Hi @Mahesh Swaminathan

Regards,

Fabian

Bill Sheboy

Hi @Mahesh Swaminathan

I recommend not changing an issue's type with an automation rule. Instead, consider cloning the issue to the new type and the abandoning (or deleting) the original one.

Changing an issue type may lead to field, workflow, and other challenges. For this reason, Atlassian has a specific function in the UI to guide a user through making the change, including asking questions to support the change. Automation rules cannot do this to support the change, and so could lead to errors or other issue problems.

Kind regards,
Bill

Mahesh Swaminathan

Appreciate the quick responses. All issueTypes within that project share the same workflow.

Also, my issue isn't that automation doesn't change issue types. Automation rule seems to do that. My issue is that the IF condition above seems to pass no matter what.

So for example: when a parent is MPP-3100 the issue type gets updated and that's good. But when a parent is set to MPP-9125, it still gets updated.

Thanks

Fabian Lim

that's because the condition is after your action.

Mahesh Swaminathan

Doh! My bad. Thank you

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