Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Moving tickets from one board to another ignores columns

Deleted user December 21, 2018

So I have 2 teams and 2 Projects, and each Project has a board and tickets associated with it.

Teams: A

  • Project: ProjA
  • Board: BoardA (BOA)
  • Stories: BOA1, BOA2, BOA3
  • Columns: To Do | In Progress | Done

Teams: Z

  • Project: ProjZ
  • Board: BoardZ (BOZ)
  • Stories: BOZ1, BOZ2, BOZ3
  • Columns: To Do | In Progress | In Review | In Test | Demo | Merge | Done 

Today, I need members of Team Z to work on tickets from Team A’s board, so I move the initial ticket “BOA1” into Team Z’s board (after modifying the filter to accept stories from Team A using labels).

The problem is that the ticket (BOA1) refuses to go down the other columns on the board. It only goes to:

  • To DO
  • In Progress
  • Done

Question:

What do I need to do to make it go to the other columns without changing BoardA structure?

Note: all the statuses that go to "In Review", "In Test", "Demo" and "Merge" in BoardZ are under “In Progress” column in BoardA

Hope this is clear…

1 answer

1 accepted

1 vote
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 21, 2018

A board is not a container for issues, it is a view of them.  Projects are the issue containers.  Issues can't "move to another board" - they are not containers, so they can't move.

If you want an issue to appear on a board, then the board must select it with its filter.  If you want an issue to not appear on a board, then the issue must not match the filter for that board.

So, you've modified the board selection for TeamZ so that it can include the issues from project A, which is the first step, but then you also need to look at the columns.  A column contains a list of status.  If project A shares status and similar workflow to B, then you shouldn't have too many problems, but it sounds like A and B have very different workflows. 

You need to account for the status that issues in A can have in your columns.  If you want to move an issue from project A from column1 to column2, then column1 must contain the current status and column2 the desired status.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events