Working with Components

Maria Szydłowska

Hi, 

I would like to learn about components in Jira Server.

I am starting my journey with this feature, so I would like to ask you non-obvious questions to avoid potential errors.

A story:

I am having a visible project A for the whole organization. This project is a home for the issues I want to organize (let's say - all bugs that are being reported in my organization).

I want all reporters to assign the issues to the Components, but the components belong to the other projects (project B, C, D, E).

Questions:

1. To make the Components visible for reporters should I give all the users from the project A permissions to create issues in the projects B, C, D, and E?
2. Can I somehow merge the same component from two different projects? (let's say that 2 projects are sharing responsibilities over the same component)
3. Can I somehow block assigning issues to more than one Component?

Do you have any interesting examples from your organization how to use Components in a smart way, to work with Jira more efficiently?

Thank you, 

Maria

 

Jack Brickey

Components are project specific, i.e. not shared across projects. When an issue is created in a project the available components are those defined for that specific project. With that said, if you choose to make your components common, replicating them in multiple projects then you could certainly create a multi-project filter and using a Dashboard gadget illustrate stats by component which would incorporate all projects in the filter. Components is a multi-select field so you can't restrict to a single entry. Using an addon e.g. JIRA Misc Workflow Extensions you may be able to use the validator "Field Has Single Value" to acheive this.