Can you add automation rules in a Next Gen Projects to clone tickets to new boards?

[Andy Tobias]

Summary:

• I would like to add an automation rule in my Dev JIRA board to clone a ticket from my Development board to a seperate release board whenever it transitions from in development -> deployed on UAT
• That way I can track the tickets that have been cloned in my Release board and I can then set the resolution to 'Done' for those tickets deployed to UAT in my Dev Board.

I can see that you can add automation rules, but it looks like I cant clone a ticket into a new board,...is this correct or am i doing something wrong?

Thanks,

Andy 

[John Funk]

Hi Andy - Welcome to the Atlassian Community!

You can certainly clone a ticket into a separate/different project/board using Automation For Jira.

[Andy Tobias]

Can you please advise what steps i need to follow to do that please John?

Thanks

[John Funk]

Do you have the rule built at all? Can you share what you have so far?

[Andy Tobias]

Hi John - this is what i have done so far.. which has not worked. both projects are Next Generation projects.

[John Funk]

So what is not working? Is it not firing at all? 

The problem might be that Next-gen Projects have separate statuses that build up. So when you select the Done status, you need to make sure it is the Done status for the Next-gen project you are working with. (You are probably seeing multiple Done statuses in the list to choose from). 

[Bill Sheboy]

Hi @Andy Tobias 

To confirm my understanding of your situation:

1. Do you have a workflow (dev and release), split across two boards for one project?
2. Or the workflow on two boards on two different projects?

In either case, after the cloning, wouldn't you change the status of the item from Done if there is more work to do: releasing?

[Andy Tobias]

Hi John/Bill,

To provide some more context...

• I currently have one board that I track all development in 
• Once the Dev team have deployed a new feature to UAT effectively their job is done and they pick up the next ticket
• Once the deployment is complete l transition that ticket to the UAT column in the workflow and continue to track that ticket in the same board until it is officially deployed to PROD
• The issue i'm having is that these tickets can remain in UAT and visible on that board for quite a while which destroys the velocity rate and makes the sprint board look crowded when no work is being done on those tickets other than testing

Therefore what I want to do is this...

1. Once a ticket has been completed and transitioned to UAT then i want to change resolution status to Done for that ticket
2. At the same time I want to clone that ticket to a new "Releases Board" which does not have a status of Done
3. Then i can then track all of the items that have been deployed to UAT without impacting the velocity rate of the Devs

Currently....

• I have tested this automation rule and found that when the ticket transitions from one part of the workflow to the next it does not mark the ticket as done nor does it clone it to a new Board
• I found that it only seems to clone the ticket if you wish to clone the ticket in the same board rather than a separate one

Please advise where Im going wrong or confirm if there is a better way of doing it.

Thanks,

Andy 

[Bill Sheboy]

Andy, thanks for the clarification and details.  That helps quite a bit.

Have you looked at the audit log for the rule to see what it indicates is happening?  That will tell you if the rule is even getting triggered, or if there are other issues.

Regarding my earlier comment, it appears that when you clone, the status is set to the first status of the workflow and the resolution is cleared.  So there should not be any need to change the status as part of cloning.

[Andy Tobias]

Hi Bill,

Below is the Audit Log that i get when i transition a task from one part of the worklfow to another and the response says "can not create issue in project/issue type"

Now their cant be anything wrong with the issue type as i use the same issue types in all the projects with the same fields, so i can only see the issue as a problem with the cloning of a ticket into a new Project.

[John Funk]

I would start by looking at the permission scheme for the target project. Be sure that the Browse Projects and Create Issue permissions are available to the atlassian-addons-project-access Project Role.