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

Feature affected by a bug?

Inna S

Hi,

when we report a bug, the reporter marks the 'product feature' that is affected by the problem.

We are migrating from another system and have tons of features in the product.

What is the preferred way to have the 'affected product feature' information in the bug?

The list of features is long and growing and we are looking to have the product owners (Dev or QA) have an ability to add entries there without the need to call for Admin's help.

Thank you,

Inna

Accepted answers

All comments

Trudy P Claspill

There is a field in Jira Software projects called Components. This is a multi-select field. The list is project specific and can be maintained by users assigned to the Project Administrator role in the project. The Components values added to one project are not available in another project, though multiple projects may have their own Components with identical names.

If you assigned your product owners to the Project Administrator role in the project, then they would not have to request help from a higher level admin to manage the list.

Inna S

Thank you, @Trudy P Claspill , this is an interesting workaround. Though I'm not sure Features can be expressed as Components. What if we need to have components too?

Trudy P Claspill

The only other native multi-select field option that is available that does not require a Jira Administrator to maintain is the Labels field. Anybody can create a Label value, and Label values are available across all projects.

The other option is to use Team Managed projects. Team Managed projects are intended to be stand alone. They don't share any of their configuration with other projects, and the workflow, issue types, and custom fields can be maintained by users assigned to the Administrator role in the project.

If you haven't worked with Team Managed projects before, do your research before having your teams go down that path. The functionality in those projects is more limited than Company Managed projects. Trying to do any sort of cross-project roll up reporting is more difficult because the configurations of every project can be different and none of those configuration items are shared.

Lastly you may be able to find an app in the Atlassian Marketplace that can provide some added functionality. I've not looked for one to solve this particular type of problem, so I don't currently have any recommendations.

Inna S

Thank you, @Trudy P Claspill . At this point we are aiming at using company-managed projects for the sake of simplicity. I also have an issue with the add-on security so trying to limit those to the bare minimum.

Do you know if we can have a user-run automation rule that would add an entry to the otherwise read-only custom multi-value field?

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud