Board Vs Software Projects

[Krista Dyer]

Hello, 

I have been using Team managed so trying to get used to the idea of Company managed and the ability to have multiple boards per software project. 

If you have multiple boards per project is there benefits to this over creating a software project itself? I have teams that will be working off their own board but we plan on using the same project templates. Just trying to decide if they need a board or a project. 

Also, how do you delete a board if you need to? I am not seeing where to do this. 

Thanks, 

Krista 

[Walter Buggenhout · Accepted solution]

Hi @Krista Dyer,

As you rightfully state: a project can have several boards. But also: a board can show issues from several projects. Boards and projects are totally different things.

When you are thinking about where you want to put your issues, there is no choice: you need a project. A project is the container you put your issues in. It is the home for your issue types, your workflows, your screens, components, versions and even permissions and notification settings.

A board is - in its essence - a tool to visualise a selection of issues. You can define which issues by specifying a filter in board settings > general. You then map the statuses of those issues' workflows to the columns of a board. And depending on the choice of board, you can organise sprints on it (if it is a scrum board) or manage a continuous flow of work (if it is a kanban board).

I prefer setting up a board for a team in your organization and bring together all of the team's work in a single place. What issues it displays then depends on what the team works on (one or many projects) and how you decide to put that work (the issues) into Jira.

Hope this helps! 

[Krista Dyer]

That does help! Do you know why when I used a template for existing project the board didn't create for the new software project? And how do I get one added to that software project? 

[Krista Dyer]

Maybe I should ask, what is the right way to duplicate a software project, board and all settings? 

[Walter Buggenhout]

Hey @Krista Dyer,

That question goes a bit beyond just projects and boards. A common (best) practice is to create a project with a shared configuration with another project. It is a step that you can select after you selected basically any template and get to the point where you enter your new project's name and key.

That approach actually shares the configuration with your other projects. If you then apply a change, that will immediately apply to all projects, which is great if that is what you want and a bit more complex when you want to differentiate later on between projects.

This approach does not copy boards. But that's actually great if you want to include your new project in an existing board. All you need to do then, is - at the worst - edit your team's board filter to include the new project. Adding a new board for a new board is also something that you can usually in a matter of minutes. It is usually just a matter of mapping statuses to columns. 

[carlos_marin]

hi @Krista Dyer ,

About your question related to delete a board:

you can go to this URL in your instance: https://your-instace-name.atlassian.net/jira/boards, you will get the list of all boards in the instance, search the board you want to delete, go to right side and click in the three dots.

Best regards,