Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Multiple boards in Business and Team Managed Projects? You bet you can!

One frustrating thing that many people have come across with their business projects as well as team manage projects (TMP) is that you can apparently only have a single board. And with business projects these boards are very basic and non-configurable. Many people want to use these projects but want the flexibility of the fully configurable boards.

I see this question all the time in the community and there seems to be a bit of a misunderstanding that you can’t have a fully featured kanban or scrum board on these projects. However that is not the case. The below instructions will show you how you can add one (or more) of these fully configurable boards to these projects. It is worth noting that it is not the most ideal solution but it does work. At least today it does.😉

The crux of the solution is to use your profile as the Location for the board since a Business or TMP software project will not be an available option under Location.

  1. create a filter that references the Business or TMP project and any desired conditions and save it
  2. go to all Boards view and select create board
  3. choose either Kanban or scrum
  4. select existing filter
  5. enter filter, name the board and for Location choose your profile (very bottom of list)
  6. save it
  7. board created. Copy the URL
  8. go to your TMP project and click +Add shortcut and paste the URL into web address
  9. result - you have a link to your new board
  10. configure the board to share as desired and any other configuration options desired.

The one con here is that the board doesn’t naturally associate to your project and appear as “the” board for the project. It won’t replace the default board but rather is a separate board and clicking the link redirects away from the project screen. However it otherwise works fine.

another possible limitation associated with ‘personal scrum boards’ is the following issue (thanks to @Bill Sheboy a for the contribution) - 


M Amine Community Leader Jun 09, 2021

Amazing article

Thanks for the step-by-step, @Jack Brickey 

Another *possible* limitation/issue of this approach was in a recent community post: sprint event changes from the profile-located board may not trigger automation rules in the source projects.  My testing showed this mostly worked for sprint created and completed, so I suggested the poster contact support for assistance.  There is an open defect for Sprint Started Trigger Not Firing for Personal Boards.

Best regards,


Jack Brickey Community Leader Jun 09, 2021

That is very interesting @Bill Sheboy a thanks for that. If you have a reference to that post I would like to review. The behavior is quite odd for sure.

My bad, @Jack Brickey as I mis-remembered the issue, which was sprint event-related.  I updated my post and added the link.

Thanks for keeping me honest.  ;^)

Jack Brickey Community Leader Jun 09, 2021

Awesome thanks! I’m going to add that issue to the article so folks don’t miss it.

Like Bill Sheboy likes this
Ajay _view26_ Community Leader Jun 09, 2021

@Jack Brickey A very good read ... I was not aware of the trick to add boards under the profile. Now that I know will use it for my daily Scrum

Thanks for creating and sharing this article, Jack! Very helpful.

I have found additional limitation with this in how issues are displayed in the Backlog. I have not figured out if there are any work arounds for these issues.

In Team Managed projects issues don't use the Epic Link field, but rather store the parent Epic issue ID in the Parent field of an issue. In Company Managed projects, the Parent field is used for storing the issue ID for the parent of a Sub-task.

This causes oddities in the Backlog display.

1. Epic issues display in the backlog, in addition to displaying in the Epics pane.

2. Child issues of an Epic are not counted in the summary for the Epic displayed in the Epic Pane.

3. To see the child issues of an Epic in the Backlog list you have to expand the Epic, like you would expand an issue to see its Sub-tasks. And in the Backlog list the child issue is counted as a "sub-task" regardless of its issue type.

4. If you have an Epic with a child Story, and the Story  has a Sub-task, you won't be able to see that Sub-task in the backlog.

In the image below I have one Epic (TNS-4) with one child Story (TNS-3). That child Story (TNS-3) has a child Sub-task (TNS-9).

In the backlog list the Epic is listed and shown to have 1 sub-task. The Epic itself does not have any Sub-task issues, but has a child Story. That Story is treated like a sub-task in the list, and it does not appear in the Issue Count for the Epic in the Epic pane. I also can't expand that Story in the list to show its Sub-task.

I also have one Story (TNS-2) that is not a child of an Epic, and it has one sub-task (TNS-5).

For this Story I can expand it in the list to reveal its Sub-task, but only because the Story is not the child of an Epic.

Screen Shot 2021-06-11 at 4.57.15 PM.png


UPDATE Sept. 21, 2022: Theses difference in display of Team Managed issues in a manually created board sounds like it is getting addressed in changes being rolled out now.

Like # people like this

Quick update, it's now "+Add shortcut" instead of "+Add Item" in #8 in the article.

Like Jack Brickey likes this
Jack Brickey Community Leader Aug 20, 2021

Thanks @Daniel Conway I have updated.

On step 4 when trying to select a filter, I get an error message:

"The Jira server was contacted but has returned an error response. We are unsure of the result of this operation."

Anyone else who experienced that? I've tried several times but still the same.

Jack Brickey Community Leader Sep 14, 2021

I have not run into that. If it continues contact support.

Thank you for this wonderfully written article. Just so I’m in lockstep with everyone else, is the terminology Business Projects referring to Jira Work Management? If not, has anyone tested this against JWM, which does not have issue types such as Epic or Story? 

Will play with this shortly but curious before I go full into this. Having the ability to manage and view multiple boards within a company managed business project within Jira Work Management is very important to our organization. 

Like Scott Hendriks likes this
Jack Brickey Community Leader Dec 24, 2021

Hi @Rehan , yes JWM is for business projects.

Like # people like this

Epic, thank you!

This is a great workaround. Thanks for sharing. However, the support for multiple boards in the same way as for JSW company-managed projects is a must.

Jack Brickey Community Leader Jul 12, 2022

@Rodolfo Romero ,

for what it's worth I don't completely agree here. While I would agree that for CMP business projects you should be able to represent multiple projects on a single board I don't feel the same way about TMP projects. .

In my opinion team managed projects need to remain silos. They should not venture into the world of CMP where you have the capability of blending multiple projects. I say this based on the original philosophy of having both CMP and TMP coexisting. If at some time Atlassian plans to jettison the CMP in favor of TMP then yes I would agree.

@Jack Brickey

If you read again my post, you will see that I didn't say "multiple projects" but "multiple boards", which is completely different to what you are describing. Boards are "views" to data stored in projects and teams should be allowed to have different views of their data. This is normal practice in the industry and many teams can get great benefits from it regardless of using CMP or TMP.

Having said that, I also think that there is value in boards that can contain information across multiple TMP. Some teams like to organize their work in separate TMP but also they want to be able to have a view (board) that aggregates the data.

The simplicity of TMP has nothing to do with the way the data is viewed. Instead, it tries to remove  the configuration complexity that CMP have.

Like Jack Brickey likes this

There is another option but only for company-managed business projects. I use different workflows for different issue types. This then presents me with a 'Workflow' option under the three dots(more) option.

Selecting a different workflow shows the status columns for that issue type(s), but also only those issues for those issue type(s). So not ideal for some, but it is another option.

This was helpful, thank you for sharing!!


Log in or Sign up to comment
Community showcase
Published in Jira Software

An update on Jira Software customer feedback – June 2022

Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...

5,014 views 18 31
Read article

Atlassian Community Events