Configuring a multi-board project

[Josh_Castiglioni]

I was hoping somebody could steer in me in the right direction, I'm trying to establish a project for the following workflow:


1) We have a reporting team that receives reports and creates issues.

2) These issues will have a custom field called "Market" assigned to them and will separate the issues to each respective team per Market.

3) The teams in each respective entry for the custom field "Market" will see their personal queue of issues and be able to work from them without having to see the results from the other "Markets". It would be ideal that each board will have separate members and hopefully get email notifications when a new issue gets assigned to their board

From my understanding I just need a Multi-board project, each board is filtered by the entries in the custom field "Market". Will I be able to create over 100 different boards within the same project assigned to multiple team members each board?

[Thorsten Letschert _Decadis AG_ · Accepted solution]

Hi @Josh_Castiglioni ,

what you're trying to achieve should be absolutely possible given the built-in functionality of Jira.

Please be aware of the fact, that boards are just some kind of view on a certain collection of issues. That said, boards could include issues from different projects and issues could be shown on different boards as well.

The configuration item of interest is just the board filter for every given board (no need to set-up a multi-board project or something like this).

Given your scenario, you could simply create a board for Team A, with the board filter including

AND MARKET = "OptionForTeamA"

etc. for the other teams (read more about configuring filters here).

Please be aware of the fact, that in order to enable your users to work with the boards you're going to configure, you should ensure that the board filter as well as the board itself is shared with your users (read more about sharing here).

Cheers
Thorsten

[Josh_Castiglioni]

@Thorsten Letschert _Decadis AG_  Thank you for your response! So instead of boards, I would create 100+ filters for each Market field option? Is there any way I can assign filters to each team, so they can get a notification when a new issue is submitted with their respective Market?

[Thorsten Letschert _Decadis AG_]

Hi @Josh_Castiglioni ,

the best approach is often highly dependant on your given configuration. However, 100+ sounds like a rather high number to me. Is your Market field holding 100+ options? Are all of the corresponding teams working within the same project then?

While default notifications might not help notifying specific teams, there are certainly available approaches - some of them needing additional apps.

Do please provide some additional insights regarding the questions above. I'm sure we'll find a valid way.

Cheers

Thorsten

[Josh_Castiglioni]

Hey @Thorsten Letschert _Decadis AG_,

I decided to go the components route, add a component for each market and that way I can assign a lead to each component and then I did quick filters if the teams want to see an actual board for the project.

To answer your questions, yes, the Market field is holding over 100 options which are small teams that will be getting issues assigned to them, and they all work from the same project.

[Thorsten Letschert _Decadis AG_]

Hi @Josh_Castiglioni ,

glad to hear you've figured out a valid solution for your use case. Quick filters might absolutely sufficient here as long as we're not talking about thousands of issues within your board. Once you're experiencing perfomance issues, you might want to split up the board in the future.

Cheers
Thorsten