Hi,
I have 2 Projects, "Project-X" and "Project-Y". I have to clone an issue between both the Projects in the Jira enterprise version.
And, If I change the status of that issue in Project-X, it must also change in Project-Y.
Example:- In Project-X the issue is in ToDo State and I change it into InProgress it should automatically change in Project-Y into InProgress.
Hey @Anonymous
This is possible via automation for Jira plugin in Jira server in case you have it ?
Please take a look at this automation answered in first comment which is very similar to your use case but the thread is for Jira cloud. But the same automation rule mentioned will work for Jira Server too.
In case if you have scriptrunner plugin we can achieve the automation there also. Have a look at this sample code and you can modify as per your requirement https://library.adaptavist.com/entity/transition-the-original-issue-according-to-the-cloned-issue
Hope this helps !
Regards,
Vishwas
Hi Vishwas,
Thanks for your response, But I do not have programming knowledge. I tried that code but facing errors.
I referred to this code --> https://library.adaptavist.com/entity/copy-an-issue-to-a-new-project-and-link-to-the-original .
Can you please help me and give me the exact solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sure, which plugin do you have ?. Automation for jira or Scriptrunner ?.
Based on that will help with code
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Anonymous
Sure, it is easier always without code :). So will try to get automation rule for you.
But one clarity, so you do clone manually or do you want that also to be automated if so based on what conditions it should get copied form Project-X to Project-Y and after that this happens rite ?
In Project-X the issue is in ToDo State and I change it into InProgress it should automatically change in Project-Y into InProgress.
Regards,
Vishwas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vishwas,
We are cloning manually and after cloning, we need these changes.
In Project-X the issue is in ToDo State and I change it into InProgress it should automatically change in Project-Y into InProgress.
Please share all automation rule steps.
Thanks & Regards,
Anonymous
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Anonymous
Automation is ready !!
Please navigate to Settings --> System --> Global automation.
There "Create Rule" and do this configuration.
Trigger: Issue transitioned
Condition: Select JQL Condition and add a JQL for your Project X and Y
Branch: For Linked Issues
Action: Transition the issue (Copy from trigger issue)
PFA
Take a look at automation playground here https://www.atlassian.com/software/jira/automation-template-library#/
Let me know in case of any queries.
Regards,
Vishwas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vishwas,
Thank you for your support. But this rule is not changing status between parent tickets. Our requirement is that after cloning. We need to change the status of both tickets.
Example:-
1. In "Project-X" --> Ticket-A is our ticket (Status- TO DO) after cloning we move this ticket to "Project-Y" and we gave the cloned ticket name Ticket-B (Status- TO DO).
2. Now, we are changing the status of Ticket-A(Status- To DO ->> In Progress) it must change automatic the status of Ticket-B (Status- In Progress).
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Anonymous
Okay .
Send me the rule what you have configured. Also log of the automation run too.
Regards,
Vishwas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vishwas,
I follow all the steps as it is you mentioned.
Please navigate to Settings --> System --> Global automation.
There "Create Rule" and do this configuration.
Trigger: Issue transitioned (Details Kept Blank)
Condition: Select JQL Condition and add a JQL for your Project X and Y (project in(Project-X, Project-Y))
Branch: For Linked Issues
Action: Transition the issue (Copy from trigger issue)
PFA
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does this issues have a link, can you please go the issues and check what kind of linking is there between them. Is it "clones" and "is cloned by" ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Figured out the issue, you need to put the both project x and project y in the scope of automation. Like this
Let me know how it goes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Anonymous
Glad I was helpful !
Please feel free to upvote and accept the answer, in case it has helped to solve your requirement
Regards,
Vishwas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Vishwas
Sorry, One more small doubt, can we do a vice-versa status change?
Example -
This is working fine that we are changing in Project-X it automatically changes in Project-Y.
But can we do small changes in the rule, that we are changing in Project-Y it automatically changes in Project-X?
Regards,
Anonymous.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Anonymous
Sure, we can do that. Just add one more option in "For Linked Issues" as clones.
So your "For Linked issues" branch should include "is cloned by", "clones". Then both ways the auto transition will work, but only check point is both Project issues should have same workflow.
Regards,
Vishwas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Vishwas
That rule was attached to one project. Here we have a different thing. We have the same case but workflows are different. For the same case, we have to write a script. We can't do it with the Automation rule. As I told you I do not have programming knowledge so help me to write a script.
Regards,
Anonymous.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Anonymous
You mean the status are different rite in both projects ?
In that case we can do it in automation for Jira rules itself. You just have to write a If else condition for each status. Trigger will be same but in the branch we need to add a if-else condition which captures the condition for status in JQL and in action we have to add change the status to particular status rather than adding "Copy from Trigger Issue".
Regards,
Vishwas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Anonymous
Sure I have tried the automation one way, like from Project X to Project Y.
You can write 2 automations like the ones shown in below.
Notice that I have given condition in JQL for one project if status is so and so then for branch in linked issues in other project of type "cloned by" change the transition to so and so.
In another rule you may have to write other way around providing other project in JQL and status, important is in branch for linked issues of type "clones"
Let me know in case of any doubts.
Regards,
Vishwas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hey @Anonymous
I would advise to create a new question in community !!
You will get more visibility and more experts will be able to suggest
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.