nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Setting Teams

Chuck Oleary_5s2ckw

In Agile development an Epic is just a large story that cannot be completed in an iteration.
Where I work an Epic is also a bucket of work that 2 or more teams will work on to complete it. Team team will have stories that roll up to the Epic. The same for an initiative.

Currently we use a multi-select custom field to chose more than one team, but oftentimes people do not set both Team and the custom field.

It would be very helpful is we could allow Epics and above to allow multi teams selections, but story and below only allows single team selection.

I'll attach a picture that illustrates my thinking.

Comments

Joseph Chung Yin

@Chuck Oleary -

Hi Chuck:

Can you clarify the following? - Currently we use a multi-select custom field to chose more than one team, but oftentimes people do not set both Team and the custom field.

What do you mean by a multi-select custom field if you are referring to the Team field provided from Advanced Roadmap for Jira components?

If users are not setting those fields properly, you can definitely setup Validator (i.e. via WF customization - at issue creation to enforce those fields to be populated before an issue can be created). Lastly, if you are referring to limiting field options (multi-select versus single select option) based on issue type, then it has to be two different fields. However, if using the same multi-select field, then it can be done via user training to guide them that they should be selecting only one option for the team field instead of trying to select multiple options.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

Chuck Oleary_5s2ckw

On Epics and above we need to assign more than 1 team to those tickets, so we created a custom field in Jira, called "Teams". We needed to do this because the built in Jira field of "Team" will only allow one team to be set.

So for stories that are worked by only 1 team it would we would set the Team.

For for larger Initiatives or Epics many teams will have be assigned to work on them.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

advanced-roadmaps

plan

portfolio-for-jira