Looking forward to this feature being rolled out!

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

This would be a very useful feature to have.

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.

Really need this feature

Our team will really appreciate this feature

Our team would greatly benefit from this. Are there any updates?

Creating multiple boards of issues in team-managed projects is quite easy to do in Coda (disclosure: I work there). You're able to view your Jira issues in a structured table and then view/edit those issues in multiple Kanban boards filtered to a team, status, product, etc. Edits are 2-way. 

Here's a quick video I made showing how one could create multiple boards: https://coda.d.pr/v/T5QkQn

Template I use in the video: https://coda.io/@atc/jira-suggestions-done-in-coda/multiple-boards-in-team-managed-projects-5

@Ivan Teong is it really such a "big" decision to implement a very small feature that is needed by so many people?

The behavior of Atlassian regarding this issue is completely contradictory to your advertising.

Currently my kanban board is saved under my personal folder. I’d like to save it under the project from which I pull the tickets. We're transitioning from scrum to kanban without creating a new project.

Also, there are 2 teams working on these tickets from end to end. We need 2 separate kanban boards to track our progress. 

Having the multiple boards for the same project is important to the success of our teams. Thanks.

Any update on this crucial FR? 

This would be beneficial. I don't push team managed projects at my org because of this reason. 

Once this becomes available, I'll be able to offload project creation to the business and really advertise team managed projects to compete with the Asana/Monday.com/trello users. 

> Can we get an update on multiple boards for team
> managed projects? We're going on 2+ years for the
> feature request 

The update is that they aren't implementing multiple boards in team managed projects.

Can we get an update on multiple boards for team managed projects? We're going on 2+ years for the feature request 

This is crap. You guys are so disappointing sometimes. So close but soo far away.

Lets be clear on a standard business usecase:

1. You have a team
2. The team does operations work - Board No.1 with Workflow 1
3. The team does job based work - Board No.2 with Workflow 2
4. The team has common access and project level requirements for both workflows
5. The team would not like to jump into two separate Jira projects to get the job done (friction)

You are missing out on a world of opportunity for a limited user experience and UX crap. Consider defining your use cases and identifying your customer needs based upon standard business operations. Work Management is a junk service. Don't try pushing the feature there. Each "template" is inconsistent and clunky due to the wide variability in process flow with no aggregation.

So disappointed to find this feature has been canned @ivan

You'll stop getting emails when Atlassian implements the solution 😂

that or... Upper right of the issue page > stop watching this issue

How do I stop getting mails about this?

+ 1 

As already pointed out it's typical that business analysis team works Kanban style while the actual delivery is done using scrum, so having separate boards is essential

+1 for this request.

It'll be great to have multiple Kanban boards in the same Team-Managed Jira Project

@Mark Crossland
@forvenus
@Aleksandr
@Alexey Turchanikov
@Artem Brezhnev
@Tom Holt

how can I reach you? (linkedin?)

Understand the general sentiment that team-projects are not prioritized at a similar level with enhancements to company managed projects. A lot of that has to do with what I'd expect is the volume utilizing company managed projects compared to team projects. We have definitely observed some limitations for some of my teams in transitioning to team managed projects. 

There have been several great features pushed within the last 2 years and also coming this quarter...

Roadmap here
https://www.atlassian.com/roadmap/cloud?selectedProduct=jsw 

Just to name two for team managed projects...

• Workflow editing by issue type - Q4 '21
• Required field support - Coming Q4 '22

I'd anticipate in time some of the gaps between features will be addressed, but we'll see. 

Very much looking forward to this as well

> This would be a very helpful feature to have!

It would. But Atlassian have decided that one of the most upvoted ideas they've had isn't actually important enough to implement. At this stage, I think that team managed projects are dead. To confirm this, I've seen no noticeable additions to team managed projects in almost 2 years of using them.

This would be a very helpful feature to have!

This is terrible .... one board view of a project ... that is a regression if you ask me...

If there's key features (like this) different between team and company managed project, there should be a notice text when user trying to make the decision.

Hope any key feature like this will be added to team-managed project.

Hi Atlassian

I believe that this feature doesn't have to be much sophisticated. At least for us it would be helpful to have multiple boards presenting different columns than the original board.

I do also think, that half way (or more) of implementing this feature is available already while allowing to configure the columns and status on origin board along with the newer feature to define not assigned status.

Those not assigned status doesn't appear on the board, but can be used to define a status for an issue.
The actual behavior is very appreciated as with it, we can focus on a two week sprint in development and the board shows the typical columns like "to do", "in progress", "blocker", "QA", done" .... (or similar)

But we also have various preparation status before a sprint starts like "collecting requirements", "verification", "ready to implement" etc... handled by Project Managers or Requirements Engineers OR subsequent after a sprint with status "Customer testing", "Approved", "Deployment".... also managed by other departments.

Of course in perspective of a development team we don't want to enlarge the board with all this status and want focus on our typical development columns. That's why we like to have not assigned status. This keeps the focus for development team, but allows to have additional status for other responsibilities.

Others can manage now their issues and change status, but it's not so user-friendly (no drag and drop, no real overview...)
The missing part is only, that other responsibilities doesn't have a board allowing drag an drop and focus on their own perspective like the preparation tasks.

Imagine how user friendly it would be to define multiple boards and assign this not assigned status to one of the additional boards, so other teams can focus on their work (not only the development team).
Imagine we have a Project Management / Requirements Management Board for the preparation work, a Development Board as of today and a Board to manage subsequent tasks when core development has been done.

I believe this would help a lot of teams out in the world in daily production. And I believe a lot of features are available already, only additional boards are missing.

Thanks, Marco

Our team is disappointed in this decision, as we are seeking some better high-level issue tracking features, and was had placed some hope in this feature suggestion to help with that current gap in the Jira Cloud offering. 

In this same vein, I've added another feature request for allowing column customization within the Issue List when viewing an issue filter at in the Detail View: https://jira.atlassian.com/browse/JSWCLOUD-23612

I hope we're able to get some of these features to allow for higher level management of a large number of open issues. 

+1

This is really needed, please add this feature soon

+1

+1 for the suggestion to have additional boards within team-managed projects. This is mission critical for our team's usage and there is too much flexibility present within team-managed projects to consider reverting back to a company managed project. 

This is really needed for the projects our teams are working in!

We need this functionality for a team managed board 

Seems you Atlassians have enough money and time to implement "improvements" with questionable business value...

Hahaha i called it! Its sad to be right but Atlassian is really dropping the ball big time. This isnt the only feature they refuse to implement or bug to fix

Big disappointment. We commonly use a dual-track approach and require a kanban board for discovery/design activities and a scrum board for development. Tasks need to flow from discovery to development. At a minimum, you should at least consider adding a dual-track project template.

@Atlassian maybe there is a basic misunderstanding here. All that is needed is that there can be more than one board per project, where one could simply configure that status 1-3 would be on board A and status 4-6 on board B and so on... boards could remain the same, statuses could remain the same, there is no new functionality needed. Has Atlassian forgotten the MINIMUM VIABLE PRODUCT approach? Why have you never discussed a simple, easy and cheap solution which could help 80-95% of the people... and then develop on from there.

I have to echo many of the comments already added. My team works with a number of different teams and being limited to a single board severely restricts our ability to review multiple teams and flip back and forth between tech work, and non tech work, that the entire teams needs to participate in during standup. Atlassian has failed miserably here and continues to disappoint. The comment from the Product Manager: "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" – it seems as though with well over "1000 thumbs up" on this feature the "CUSTOMERS" have indicated that this is a priority. So much for customer centricity take precedent over profit.  

Why does such a simple small feature need a "project"? Just do it... you are selling software for agile companies, yet you are not agile at all.

Huge disappointment as well. It can't be that hard to do that. 

For sure we don't know as users what is lying behind this decision, but from the user point of view (isn't it that what agility is about?), this outcome is terrible - It looks like the Atlassian suite is not a good match from Product Managers after all.

We're very disappointed in this decision. Unfortunately, this decision means that we will likely be looking elsewhere for our PM system. Our decision to move to Jira was hinging on this feature, as we identified it as critically required functionality.

For us, boards model processes and I don't think any team can truly run with just one process.

My assumption is that this means tasks are actually prioritized based on profitable enterprise customers and votes are secondary, if not entirely meaningless. It makes sense from a business standpoint.

However, it's certainly disappointing after such a long wait and constant pushbacks and delays giving the impression that the feature is well on its way but tricky to get right. It also drives in the point that the concerns of smaller teams don't matter for Atlassian and the best option in the long run is to look elsewhere for project management needs.

I don't understand the point of considering this for the future after waiting for 4 years. This is one of the most voted features; unfortunately, Atlassian didn't recognize this. I wonder how Atlassian prioritizes the feature backlog. 

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.

Having migrated from an on-premises solution to a Jira "team-managed" project because "this was the future", we're now told that we have to migrate again to the "company managed" solution in order to get what we need?

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.

I appreciate the apparent honesty, but noting that this issue has received 1,196 votes but still isn't deemed important is extremely disappointing. Especially as I have seen examples of features with less votes than this getting implemented, so this bit rings hollow.

Other than those items, I've seen little to no improvement in the team managed projects in the 2 years I've been using them. Certainly no new features or visible changes and my personal opinion is that team-managed projects are dead.

Time to look into another solution. The Microsoft Planner application is very good.

Oh well... 4 years and all you get is nothing... that says a lot about Atlassian as a company.

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

1. 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.

1. 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.

Regards,
Ivan Teong
Product Manager, Jira Software

Indeed, we're going to switch back to the normal-gen type, as next-gen is not being developed

Is next-gen dead?