-
Suggestion
-
Resolution: Unresolved
-
1,346
-
115
-
Summary
Jira Software Cloud users would like the ability to create multiple boards for each team-managed (formerly next-gen) project, just as they can with company-managed (formerly Classic) projects.
Workarounds:
- Use “dummy” inactive sprint containers in the team-managed backlog as placeholders for different types of work like “design”, “QA”, “eng health” and “feature work”. Pull issues into active sprint container representing the board when the work is prioritised and ready for sprint.
- Use different team-managed projects to represent different types of work, if the workstreams are totally distinct and separate, and doesn't require any form of "syncing".
- Use company-managed projects (but you will have to deal with project schemes for project setups).
Hi everyone,
We have an important message to share about the development of multiple boards for team-managed projects (TMP). We believe that it is important to be transparent with our priorities, and what features we are and aren’t working on.
Unfortunately, we’ve decided to pause the multiple boards project as of May 2022. We are still committed to continuing investment in TMP, which you can see here in our public roadmap
- Over the past few months, we conducted an extensive review of the needs of all our customers and came to the conclusion that in order to double down on our efforts on scale, performance and reliability of our products, we had to pause work on multiple boards.
- In the meantime, if you need to have multiple boards in a single project and are unable to work with any potential workarounds listed in the description of this Jira ticket, we continue to recommend teams to use company-managed projects. We apologise for the inconvenience that this may cause you.
This was an incredibly difficult decision for us to make. We know that so many of you have been eagerly awaiting this capability, and that this update will cause some frustration.
The long term direction of TMP is still to support the needs of multiple teams working together, but it is our duty to look at our entire customer base and ensure we're investing in the areas that will bring the most value to the most customers.
We plan to re-evaluate our roadmap and revisit this decision every year. We will share an update if anything changes. Do vote for this feature and watch it to be across any new updates.
On behalf of the Atlassian team, we take your feedback seriously and understand both the frustration and the urgency.
Note:
We’ve gone through all the feedback specified in this Jira ticket and identified feedback which represent separate feature suggestions. You can vote for these other feature suggestions below:
- Cross-project roadmaps and boards: Pull in epics or issues from other projects to display on your roadmap or board, in order to enable cross-team visibility for planning and tracking work:
- Cross-project roadmap: https://jira.atlassian.com/browse/JSWCLOUD-20703
- Cross-project board: https://jira.atlassian.com/browse/JSWCLOUD-17444
- Multiple active sprints: Manage 2 or more concurrent active sprints:
Thank you,
Ivan Teong
Product Manager, Jira Software
- is duplicated by
-
JSWCLOUD-17912 Create a Board from an existing NextGen project
-
- Closed
-
-
- Closed
-
- Closed
- is related to
-
- Closed
- mentioned in
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
[JRACLOUD-85686] Allow multiple boards in team-managed projects
Hi all,
Thank you so much for your votes and comments on this suggestion.
We are doing further research on this topic and would love to invite you to take part in an upcoming customer research study!
What’s involved in the research:
- Sessions are 1 hour and conducted over video-conference, so you can participate from anywhere around the globe.
- During the research, we'll start with a general chat to get to know you, then explore a prototype and complete some tasks.
- As a token of our appreciation, you'll receive an e-gift card worth $120 USD within 5 business days of completing your session.
Interested in taking part? Follow this link to fill in a few more details so we can make sure you’re a good fit.
If you have any other questions at all, feel free to reply to this message or email me directly on rpit@atlassian.com. We look forward to meeting you!
Cheers,
Ruvi Pitiyarachchi
Design | Jira Transformation
As with any task on a Jira board, communication is key. It would be nice if an update was posted more often. There are a lot of comments with no answers and that is why people get frustrated and don't think you are doing anything to resolve this issue. Put in an update every quarter at the least. This issue has been going on for more that 2 years with no clear direction. I would think that Atlassian could work on more than 1 issue at a time. Team-managed board are easier to create for users.
it is our duty to look at our entire customer base and ensure we're investing in the areas that will bring the most value to the most customers.
1659 votes. 621 watchers. This is the fifth most voted for feature that I can see on Jira. So the above statement does not make any sense.
We plan to re-evaluate our roadmap and revisit this decision every year. We will share an update if anything changes. Do vote for this feature and watch it to be across any new updates.
I am assuming that no news means this feature is abandoned. Or hasn't been reviewed.
That's really needful, especially after migration from on-prem
iteong are you going to do something against Atlassians behavior to classify bugs as features and then, together with all the other VERY demanded features, never implementing them, while implementing new fancy stuff that nobody needs?
This is basically the most crucial missing feature for not choosing a team-managed over a company.
Looking forward to this feature being rolled out!