How to assign a component for the client organization?

[Developstores]

The client selects the component when creating an issue on the support portal. I have several clients for whom I developed programs (components). How to restrict the visibility of components for the client organization?

Or do I need for each client to create a separate support project with the portal?

[Hazwan · Accepted solution]

I would actually go with a separate project, just because, you can't restrict the visibility of components. Components exist in a project. Different project can have a different component. But as for one project, JIRA would pull all the available components on the project for the user to select. No restriction applied there.

[Developstores]

Through the helpdesk was asked to develop an application for the site. For development, I create a new software project. In the support service, can i link the component to the development project? Or it is necessary most to control and understand what component belongs to the certain software project?

[Hazwan]

The latter is what I would recommend. A component is rather a field for a particular project. There's really no option to pull the component details to a different project. Perhaps, you can have the same component added to the project?

[AhmadDanial]

Hello, Oleksiy.

Components are specifically tied to projects, meaning that you can have the following set up as an example:

• Project A
  • Performance
  • Network
  • Database
  • LDAP
• Project B
  • Administration
  • Integration
• Project C
  • Development
  • Release
  • QA

If a user chooses Project A when creating a new issue, the user will only be able to see Performance, Network, and Database under the dropdown list in the create issue screen. So, the visibility of Components is already restricted there.

In your case, are you looking at a master Component page where you can assign component(s) to be present for specific project(s), pretty much all under one roof?