Board displays multiple issue types from different projects but needs a new workflow status
Asked by Spasimira Genova:

Hi everyone!

Our UX Writing team is using a board within our Design project and this board visualizes multiple issues from multiple projects who have the label 'ux-writing'.

Currently they need a new status called "Rejected" in order to sort tickets they don't have capacity for. It would be quite difficult to create an actual new status as like I mentioned their board visualizes multiple issue types from various projects and that would be a major change.

Is there a workaround for this?

Many thanks!


Answers:
author: Tim Kopperud
body: Hi [@Spasimira Genova](/t5/user/viewprofilepage/user-id/5468025), if I understand you requirements correctly you will not be able to do this. A board column is mapped to one or more statuses. You cannot have tow columns using the same status.

I had the same requirements a few years ago, and we solved it by adding the status, but the transition to this status was only visible for a specific team hence other teams did not relate to this status at all.

If this is not an accepted solution for your requirements (I understand it is not), then the following workaround might help.

Use a field (lables, resolution or customfield) to mark the issue "Rejected" (or something), then in your board, filter out all issues tagged as Rejected. If you need to see them for a while on the board, include a time limit in the filter for these issues. You might also define a dedicated card color for these issues and a quick filter for hiding them.

TimK.

comments: author: Spasimira Genova
body: Hi Tim,

Thank you for your reply!

We have decided to go with the second workaround you've described - turns out all issues from these project share a status called 'Cancelled'.

We will create a label 'rejected', and a quick filter for the UX writing team's board that shows tickets with this label. Then the team will manually put those issues in the cancelled status along with issues cancelled for other reasons.

Many thanks!


author: Tim Kopperud
body: Hi [@Spasimira Genova](/t5/user/viewprofilepage/user-id/5468025), great. Thanks for accepting the answer.

TimK


author: Lucas Lombardo
body: Hello!

I found myself in a similar situation (a board displaying several issues from different projects with different statuses).

In my opinion, if you create a "rejected" status, the most important thing is that this status should be mapped to the appropriate columns on each board. For example, if the UX team sets a ticket to "rejected" it can be pushed to the "on hold" column in another team's board (although it will still have the rejected status).

If you use this new status, teams that have never used it will see this status as "unmapped" by default in their configuration board, and unfortunately I don't think there's any other option but to ask each board owner to map this status with the appropriate column.

The last possible option, which will also depend on what you want to do with rejected tickets, is to create an automation so that rejected tickets become cancelled, but I imagine that these tickets will wait in a backlog?

Good luck, I hope this helps :)

comments: author: Spasimira Genova
body: Hi Lucas,

Thank you for your input!

The first option is going to be too complex to implement for our current ways of working. The latter is a good idea but we are limited in terms of automations as we are on a standard subscription plan.

Both are very good workarounds in any case. :)


Tags: cloud

jira-cloud