Is there a way to move issues to a diff team's board in JIRA after the issue is resolved in sprint? Edited

Is there a way to move issues to a different team's board in JIRA after the issue is resolved in my team's sprint?  I would like to move issues to a different team's board in JIRA after my team closes them in order for the issues to undergo the UAT process, which will be led by a different team and different workflow.  I would like to avoid adding sub-tasks to my team's sprints as the UAT process will undergo different worklow steps and under a different cycle time.


Also, I do not want to lose the data that tells us when the ticket was complete within the development sprint.


Any ideas?

3 answers

2 accepted

2 votes

>move issues to a different board

No, because that's an incorrect assumption about how it works.  Boards do not contain issues.  Projects contain issues.

Boards show you a view of a set of issues. 

What you want to do is set up the boards so that when an issue reaches a point in its lifecycle, one board stops selecting it and another one starts to.

There are a couple of really easy ways to do this.  Imagine a workflow is generally:

New -> in dev -> ready for test -> in test -> done

Option 1:
Board 1 for devs has columns for New, in dev and ready for test.
Board 2 for testers has columns ready for test, in test and done.

Option 2:
Board 1 filter: project = abc and status in (new, in dev, ready for test)
Board 2 filter: project = abc and status in (ready for test, in test, done)

Makes sense.  Can you help add sprint & board type to your example?  Say Board 1 is a scrum board that uses a 2 week sprint and Board 2 is a kanban board.  How do I understand that the team for Board 1 met sprint goals?  Is the sprint for Board 1 closed in the same way as before?

The board types don't matter here.  Board 1 selects a load of issues and allows the users to work with them in either Scrum or Kanban ways, depending on the board type, and board 2 does the same independently.  They both act on the selection they make from the underlying list of isssues, so changes in one affects what the other sees, but they don't really interact directly.


In our development workflow, the last step for the developer is resolved.  The next step is for UAT.  if UAT passes, then to deployment and closed.  We are recording UAT date time with UAT notes, deployment date, and closed date.

The UAT board is filtered to only show those issues in UAT.

Another option is that if you have script runner, on resolution as a workflow post function, the issue can be cloned as a differnt issue type

Makes perfect sense.  Thank you to both of you for your replies.  Appreciate it!

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,210 views 13 19
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot