Is it possible to automate tickets to move to another board

Mihir Ruparelia

Hello, 

I have been tasked to improve the flow of a current requests board that we have set up and part of doing this is having tickets be moved from one board to the other. 

Scenario: 

Ticket comes into board A, it gets to the Approved stage, at this point we have an Actions button as part of our work flow, depending on what is selected the ticket should in effect move across to another board. 

What happens currently is using Deep Clone the ticket fields are cloned to the destination board. But what is required now is the ticket only sits in that destination board. Otherwise it gets quite messy dealing with 2 different tickets for the same thing. 

Is it possible to do this? If not is there an alternative solution. 

Any help would be great. 

Michael Andolfatto_a62ntx

Hi @Mihir Ruparelia ,

This is definitely something that can be done. First, I just want to call attention to the difference between Jira Projects and Jira Boards.

Jira Projects

Workspaces for one or more teams that contain related issues

 

Jira Boards

The visual board + backlog which displays a set of issues from a JQL filter

 

---

Moving an issue from Project A into Project B can be done manually (through the Move operation) or automatically via Jira's native automation tool. Jira Boards on the other hand, can display issues belonging to multiple projects since they are powered by a JQL filter.

In your use case, TICKET-001 comes into Board A. A board from another project can still display this issue (while TICKET-001 continues to live in its original project) once a certain condition has been met. If the "action" is to change its status or a custom field value, Board B's JQL just needs to include this in its query. In addition, you can modify Board A's JQL so that this issue no longer displays on it (even though the issue still lives in this project)

 

Alternatively, you can use Jira's automation to specify that when X Action happens, Y Issue should move to Z Project. This will likely need to be configured by a Jira Administrator in the Global Automation menu since the scope affects more than a single Jira Project.