Move issues to different board on transition to specific status

Hi everybody,

I'm currently in the process of trying to figure out how to automatically move issues from one board to another, and I'm having trouble finding a solution. To clarify let me explain why I want to move them:

Currently my company has several departments. The technical department is in charge of system administration, web development and development of the inhouse software. Right now only the technical department uses JIRA , but we want to expand to the other departments as well. One of the things that will happen a lot is that an issue will be created in the technical departments board, go through several transitions there, and on transition to for example a Test status, need to be transferred to the board of the department that requested the issue to test. At this point they'd go through their workflow and might discover something that would require it to go back to the technical board, or set it as Done there.

From what I understand moving issues automatically is a pain in the behind, but simply cloning the issue to the other board wouldn't fix the part of the process where the issue would be sent back to the first board. Then you'd have to somehow sync the two issues, and I haven't found a solution for that either.

Any suggestions would be appreciated.

1 answer

1 vote

Let's start with the flawed assumption in the question.

Issues do not "move" between boards.  Boards select issues based on the data on the issues.

This actually makes the solution for your case very simple.  You set up one board holding some of the steps in the workflow, and another board with other steps.

Let's say you have a workflow who's ideal path is

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

A board for the developers should have three columns with status in them of New, in dev, and waiting for test.  A board for the testers then has waiting for test, in test and done.

 

You're correct, there's no moving between boards, I got that mixed up with projects. Of course, if I was to add an Agile board with an In Test workflow, that'd still be in the same sprint. Since it'd be a completely different department running the testing part they'd have to use both their own project and board, and then additionally use the In Testing board of my departments project. 

You don't need to have a separate project, just have a board that shows issues in the status each team is interested in and not the ones they don't care about.

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,316 views 14 20
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