Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

Mahesh Swaminathan January 20, 2024 edited

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

3 answers

1 accepted

4 votes
Answer accepted
Fabian Lim
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 20, 2024

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

0 votes
Mahesh Swaminathan January 20, 2024 edited

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
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 20, 2024

that's because the condition is after your action.  

Mahesh Swaminathan January 20, 2024

Doh! My bad. Thank you

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 20, 2024

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

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
atlassian, atlassian government cloud, fedramp, webinar, register for webinar, atlassian cloud webinar, fedramp moderate offering, work faster with cloud

Unlocking the future with Atlassian Government Cloud ☁️

Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.

Register Now
AUG Leaders

Atlassian Community Events