How do I create and manage multiple boards on my jira project?

[Jerred Cook]

We use scrum and kanban boards to represent agile teams in Jira Datacenter.  Each agile team has at 1 board for their work.  There are multiple team's in a single project.  Each of these teams has their own board.

How do we replicate this in Jira Cloud?  Or....what is the recommended way to model a team in Jira Cloud?  Is it one team per project?  Jira DC recommends one team per board and many teams per project....

Please advise.

[Trudy Claspill]

Hello @Jerred Cook 

Welcome to the Atlassian community.

You can do the exact same thing for Company Managed Software projects in Jira Cloud. Those projects are equivalent to the projects you worked with in Jira Data Center. As in Jira DC you can create and save filters to select a subset of issues from 1..n projects, then create a new agile board based on that saved filter.

There is another type of project available in Cloud called Team Managed Software projects. These target a slightly different audience where the team has control over the customizations and doesn't need more than one agile board.

The model you should use depends on the needs of your company. If the model you are using in Jira DC works for you, you can continue to use that same model in Jira Cloud.

[Jerred Cook]

OK, how do I set up a "Company Managed Project"?  We wanted to set up a "Premium" account for about 50 people but it only lets us setup "Team Managed Projects" with only one board.

We setup the free trial but it expired before we could figure it out.

[Jerred Cook]

Also, would the "Team Managed" projects imply that there is only one agile team per project?  Why would that be useful if the paradigm is supposed to be multiple teams per project as in JDC?

[Trudy Claspill]

Company Managed projects can be created only by the people with the Administer Jira global permission, similar to the Jira DC environment. 

By default a new Jira instance is configured to allow anybody to create a Team Managed project. That is another Global Permission.

When Jira Admins create new projects following the familiar path of going to the Projects menu and selecting Create Project. They are give a list of project templates to select from. At a later step in the process they can choose whether that project should be created with the Company Managed architecture or the Team Managed architecture.

The trick is if they get to the point of entering the project name and key, and they DON'T see this option:

...then they are about to create a Team Managed project.

Also, would the "Team Managed" projects imply that there is only one agile team per project?  Why would that be useful if the paradigm is supposed to be multiple teams per project as in JDC?

There is no paradigm dictated for using Jira Cloud. Clients of Atlassian have expressed differing needs. Many want centralized control of project configuration as it has existed in DC. Others want to decentralize that and allow the teams to manage the customizations of their projects independently. Team Managed projects serve that second client need.

Team Managed projects only offer one built in board with the project. It is possible to create saved filters for those projects and create boards based on the saved filter, but the board does not display in quite in the same way. There are a few architectural differences between the two project architectures that cause this. Team Managed projects also do no yet offer all the same workflow customization options as Company Managed projects.

If you are comfortable and content with the way you do things in Jira DC I would recommend you continue on that path as you move to Jira Cloud.

[Jerred Cook]

I would like to follow exactly what we do in DC but I am unable to do so.  Please advise.  

I see this message when trying to setup a Company Managed project:
Contact your Jira admin to use this project type.

I should be the Jira admin.  We are trying to setup a new "Premium" account.

[Trudy Claspill]

If you are getting that message when trying to create a Company Managed project then you do not have the Administer Jira global permission. 

The person who created the site and the Atlassian Cloud Organization under which it exists would have the highest level permissions. There are other administrator roles that may be granted but the exact roles depend on the type of User Management used in your Organization. Atlassian has been rolling out a change to that so some sites have the Original UM while other have Centralized UM.

https://support.atlassian.com/user-management/docs/what-are-the-different-types-of-admin-roles/

https://support.atlassian.com/user-management/docs/give-users-admin-permissions/

You'll need to work with the Organization Administrators for your Atlassian Cloud Organization to get access to be a Jira Administrator.

On a side note will you be attempting to migrate your Jira DC data to your Jira Cloud instance, or are you intending to start fresh in Jira Cloud? Data migration can be a very involved process. In either case you may want to consider engaging with an Atlassian Solution Partner for some of all phases of your transition to Cloud. You can find partners in the Atlassian Partner Directory.

Disclosure: I work for Praecipio, and Atlassian Platinum Solution partner. We have several specialization that you could leverage to make your transition smoother.

[Jerred Cook]

How do I find out who that person (Organization Adminstrator) is? 

[Trudy Claspill]

Unfortunately there is nothing you can do on the system as a non-Admin to try to get that information.

In the Jira product, if it has been activated by the Jira Administrators, you may find a "Contact Administrators" option under the Help icon near your avatar. They may not have activated that option.

You can start by asking the person who told you to access the Jira Site you are currently using. If they don't know who the Org Admin is try to trace through to the person that told them to tell you to access the site. Try asking the tech support team for your group and your company. 

You may even attempt to get the information from Atlassian support directly, though they must adhere to confidentiality policies and may not be able to give you that information.