We are currently using Jira Cloud. When configuring boards' columns status bindings, we have statuses that are "duplicated" but only in the board's status list. There's still the only one status in the instance's status list. It's becoming quite a hassle to distinguish which is which when configuring boards. Like so:
As you can see, there are 14 Done statuses available... When only 1 real one exists in the instance's statuses list. We have, however, 14 statuses with the "Done" status category... So what I suspect is that the Done status is "duplicated" as many times as the Done status category is associated with a status. Note that the duplication happens with the "In Progress" and "To Do" as well since they are both statuses and status categories.
Only these 3 statuses that are both statuses and status categories are affected which leads me to think the problem lies here.
Anybody has a solution to solve this?
Thanks in advance everyone!
Ah I think I’ve seen this before.
The filter for your board is pulling in across multiple projects in Jira. If those projects are not using a standardised workflow with similar statuses (and by similar I mean unique based on ID not name), then the board will display all the statuses for all the projects.
Thanks for the reply. The boards' filters are indeed quite broad and are pulling issues from multiple projects (2 of them being next-gens) with their own workflows. Would there be a way to solve that problem without needing to use the same workflows for all the projects?
If you’re only creating a handful of boards that are cross project, get the correct Done statuses mapped and then clone this board for future boards.
This will be trial and error of moving them in and out of the column until you know you’ve got only the ones that apply to the project.
You could look to rename the status after the project .. (just thinking out loud .. I.e. Proj1 Done; Proj2 Done; etc)
Once it is all done, just tell the board admins not to look at the Unmapped status column as their eyes might bleed.
@JiraJared , I'm also facing this same problem.
You wrote "If those projects are not using a standardised workflow with similar statuses (and by similar I mean unique based on ID not name)", but when you create statuses in Jira, they already get a unique ID. I only have one Done and one In Progress (and obviously one ID per each), so I still can't understand that duplication. Can you please elaborate?
This also can happen with Next Gen I find if you have those projects in this view.
If you filter Next Gen projects onto a Classic Board, it duplicates statuses. I expect this is because as each Next Gen project is meant to be separate, it is treating those statuses as unique albeit they have the same name.
@Ronan , I’m quite confused by the image you have posted here. Is this an image of Board settings > columns? In that view you should see “statuses” in the columns. Status categories are a different matter. For example, let’s say you have two statues (Closed, Done) of Status Category = Done and you mapped them both to the “Done” column then you would see Closed and Done in that column, not Done, Done. Make sense?
now, back to your situation. If you are seeing this on the column configuration view then that is one for the books. I cannot see any way of having more than one (1) “Done” status in that view much less 14.
I have to admit I’m not sure where to go next with this. I might simply be tripped up by a simple config issue here but not seeing it. I will reach out to others to see if they can assist.
in the meantime if you have any more thoughts on this please share.
Thanks for the reply. Yes the screenshot I added is a view of a board's column configuration page with the highlighted statuses being in the unmapped column. And yes, the statuses and their categories are different indeed. My assumption (which is most likely wrong) was that since we had the same number of statuses categorised as done as the number of "duplicate" unmapped statuses, the problem might come from there.
As mentionned by JiraJared below however, our boards' filters are quite broad and encompass multiple projects (2 of them being next-gens) with their own workflows. I am now suspecting the real problem to come from there.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events