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

Automation rule on status change of jira ticket.

Neeta Dubey

Hi All,

I need help in creating a jira automation.

Scenartrio:

I've a ticket in Project A and clone of that ticket in Project B.

Once the status change of that specific issue type ticket it should change status of that cloned ticket in project B. Is it possible to achive?

Accepted answers

Marco Brundel

Hi @Neeta Dubey ,

In an automation rule you can specify Issue transitioned as the trigger. And in a rule you can include a Branch where you then define an action in the branch for, for example, the linked issues.

Can you continue with this information?

regards, Marco

Screenshot 2024-04-04 at 14.16.25.png

All comments

Marco Brundel

Can you continue with this information?

regards, Marco

Screenshot 2024-04-04 at 14.16.25.png

Dexter de Vera

Hi @Neeta Dubey ,

You need to create 2 automation for creation of clone ticket to and updating status.

Automation 1:
When: Issue created

Condition: Issue fields condition - Project - Project A

Then: Clone issue - Project - Project B (You can add more fields changes if you want)

Automation 2:

When: Issue transitioned - leave it blank status from and to so all every changes in status will trigger the automation

Condition: Issue fields condition - Project - Project A

Branch rule / related issues: Branch rule / related issues - "Type of related issues = Linked Issues" and "Link Type = is cloned by"

Then add Action in the branch - Transition issue - Destination status - Copy from trigger issue.

NOTE:

Both project should have same workflow.

Dont remove/update the linked issue because this is the way to track the clone issue.

The scope of both automation should be Project A and Project B (you can see this under Rule details)

Hope it helps!

Neeta Dubey

Hi Dexter,

thank you so much for info it works well when cloned issue is in the same project although I've included both the projects in scope.

it faild when I did below -

I created defect in Project A, cloned it, moved the clone to Project B, change the status of the mqms defect in Project A, and the status of the Project B defect didn't change

Dexter de Vera

Hi @Neeta Dubey ,

Do you create the 2 automation? First automation will directly create clone issue in Project B. No need to manually clone then move to project B. And the second automation is the one will update the issue clone base on the transition made in project B.

Maybe you can show us the 2 automation you made so we can check it.

Neeta Dubey

Thanks Dexter, When I move ticket from Inprogress to Implemented, I've a transition screen and some validators, which is same in both the tickets, would that we causing the issue.

Also, I didnt automate it because I don't need to clone issue every time, is manual cloing is a problem snip 3.png .

Also, i modifed the condition to "Clones" as I would be making changes in the cloned issue.

This works well when I dont have any transition screen like moving between to do to backlog.

Dhiren Notani_Exalate_

Hi @Neeta Dubey ,

Thanks for posting your question here on the community.

I am Dhiren, one of the Solutions Engineers working at Exalate.

Although it might be possible to do this via Jira Automations, but the more robust and flexible way to achieve this is using a dedicated and fully decentralized integration solution like Exalate.

Exalate uses Groovy based scripting engine which offers you limitless customizations, and not only you can sync issues seamlessly, but with that you can choose what fields to map (even custom fields of any type can be synchronized).

Thanks, Dhiren

Welcome!

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

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

automation