Hi Support Team,
I am working in a Business Space (Company-managed) project called ACCOUNTING, and I have 3 different workflows with different issue types and different status sets:
What I need: I need 3 separate boards, one per workflow, where each board only shows the relevant statuses and columns for that specific workflow.
What is happening:
Previously, there was a simple way to switch the board view depending on the selected workflow. This no longer seems to be available.
My questions:
Thank you.
Hello @philip_veselov
Welcome to the Atlassian community.
Can you provide screen images to show us what you are seeing in the boards you are describing? Obscure confidential information.
What steps did you execute to create the second board?
Can you provide links to any documentation you used as guidance?
Hi, thank you for your response!
Here are the details you requested:
Screenshots: I am attaching two screenshots showing the issue:
Steps I used to create the second board:
The core problem: My project has 3 workflows with completely different status sets (AP, AR, and Tasks). When all three are present on one board, Jira switches to Advanced mode and locks column editing. Statuses from AP and AR workflows get pushed into "Hidden statuses" and are not visible on the board.
before jira was updated, I could create a workflow and mix between these processes on the board without creating more boards, now there is no such thing
Documentation I referenced:
Thank you for looking into this!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @philip_veselov
Thank you for those screen images. That is helpful.
Is the first board showing statuses from only one of the workflows? Or are there more columns off to the right with more statuses so that all statuses from all workflows are included?
So far I have not been able to recreate this situation. I've been asking Chrome Gemini. It has not provided an answer for which I am able to replicate the conditions.
This post has been flagged to raise it to the attention of Atlassian team members. Hopefully they will be able to provide some insights.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.