Using Components - How Rich Is This Feature/Capability?

[MikeekiM]

I am new to Jira, so thank you in advance for your patience.

I have created components... So that I can make it real, let's say I created three components for a product/project:

- iOS Mobile App

- Android Mobile App

- Server

Let's say I create an issue called: Add Search Capability

I assign all three of the above components to this issue...

What does this assignment allow me to do? Is it simply a means of filtering (e.g., I can filter out all the issues that have Android Mobile App as a component)? Or can I do other planning things like assign work effort by component within an issue?

I am hoping that I can do the latter... Or if not, I guess that means that I have to create three sub-tasks for each of these components...

Can anyone help me understand how rich this component capability is? After looking through the tool, it simply looks like a means of categorizing the issue with multiple components for searching and filtering only (which is pretty limiting in my opinion).

Thanks!!!

Mike

[Faisal · Accepted solution]

Hi Mike,

JIRA components can basically be used to group issues together, based on their common components. Other than that, we can also track the total work effort (based on the number of issues having that component) required per component basis.

Let's say for a given project, there may be n number of components involved. Therefore when creating an issue, we can 'categorize' the issue based on the component which it may be related. Hence, some issue may have a specific component assign to it, but for a larger issue, there may be a couple of components specified to the issue. And if the latter is the case, it is best to further breakdown the issue into multiple subtasks under it.

You can also assign a component lead to each of the components that you have created. This basically allows you to manage the components better, given that you have a large project that you are working on.

And of course, you can use issue filtering to search for issues based on their components. :)

Anyway for self reading on components, you may kindly refer to the following documentation:
- https://confluence.atlassian.com/display/JIRA/Defining+a+Component

I hope that this will help!

[MikeekiM]

OK... So based on your reply, my interpretation is that it does not provide much more intelligence than a simple multi-assignable category...

By adding the components to an issue, I can see all of the issues that have that component associated with it... And as a result, I can see the total work effort of all the issues (but not necessarily the work effort for just the component itself across multiple issues).

If I want to see the work effort by component, I should create a sub-task for the component and assign the work effort to the sub-task...

Do I have an accurate picture? Or am I missing something?

Thanks!

[danielwester]

Components can also ave owners which you can utilize in workflows (default assignee), permissions and/or in notifications. There project view also has a mini project view around components.