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; } } }

Fields used to logically group defects in components

Ahmed Muneer

The project in which i am working has many components. Multiple QA teams distributed geographically are working on the same components Project Manager wants to analyse the defects logged by a particular QA team. Given this scenario, what are the fields he can use to logically group defects?

Labels or Custom Fields or both?

Accepted answers

Nic Brough -Adaptavist-

Either would do it.

I'd be tempted to create a simple group-picker field for this, and then think about scripting it so that when an issue is created, the field is set to the group for the team (it would need to make assumptions if the reporter is in more than one of the groups you're interested in)

All comments

Nic Brough -Adaptavist-

Either would do it.

Ahmed Muneer

So you mean Labels and Custom Fields? Is group-picker falling under custom field?

Nic Brough -Adaptavist-

For what? I said you could use either (or both)

Yes, a group-picker is a custom field type.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud