Components

[Louise Kidney]

Does anyone have a link to a good video that outlines scenarios and examples of how components are used?  Thank you.

[Crystelle S · Accepted solution]

I've heard that they are all a bit frustrating.

From Atlassian's archives, components were originally meant to represent modules within a codebase or systems within a software stack as Jira projects were originally intended to be software that released together.

A lot of consultancies have recommended Jira projects be wrapped around Teams without that nugget of information so I have also seen Teams use them for systems that they are committing code to - invariably someone becomes frustrated by having to enter the same release into multiple projects and laments that the system "could be so stupid not to share them".

[Louise Kidney]

Thank you Chrystelle.

[Sachin Dhamale · Accepted solution]

@Louise Kidney ,

Jira project components are generic containers for issues. Component are used in multiple ways like module or department or specific entity in the organization and many more. Components can have component Leads: people who are automatically assigned issues with that component. Components add some structure to projects, breaking them up into features, teams, modules, subprojects, and more. Using components, you can generate reports, collect statistics, display them on dashboards, etc.

Project components can be managed only by users who have project administrator permissions. They should have unique names across one project. Nothing prevents users from adding issue to more than one component.

So you can automate assignee based on component

Accept the answer if it helps.

[Louise Kidney]

Thank you, Sachin.

[Louise Kidney · Accepted solution]

Here's one video I found that provides a quick explanation

https://www.youtube.com/watch?v=Aq0V_iaaCMQ