Workstreams - one program, multiple teams - custom field?

[Marieke Bouwman]

Hello community,

For a bigger Program of work we want to have all tickets living within 1 Jira Classic project (this is 'must have' and needed for multiple reasons).  This Program has multiple workstreams (different teams).

Here is my question:  Is there a custom field that can be used to make sure tickets 'land' on a specific board (1x Jira Project and 2x Workstreams (teams) with each their own backlog and board). How do I make sure certain tickets are 'seen' for a specific team and not for the other team.

Target scenario: Jira Classic Project AB 

Team (Board) A, seeing tickets tagged or labelled with A (> what custom 'field' to use? ) 

Team (Board) B, seeing tickets tagged or labelled with B (> what custom  'field' to use? ) 

Thank you !

[Nic Brough -Adaptavist-]

Welcome to the Community!

You have almost answered your own question - use a field to distinguish between teams.

Boards are based on filters, they select a set of issues based on a question.  The usual question is simply "project = xyz", but you can change the filters to do something like "project = x and field = y" for Team A and "project = x and field = z" for Team B.

The decision as to what the field is is a little difficult, it depends on what might work best for you.  You could use a simple custom field like "workstream" with a dropdown llist with two options, or labels (problem there is people could use any word and get it wrong), or components (but that's multiple select which may be confusing), or even a simple "field empty = A and field not empty =B", or, or.

 It's up to you how you define the workstream really.  If you can tell us a rule for identifying workstream from the current fields, you could do it with a more clever query, but an explicit field might be the easiest thing