Documentation for JIRA 6.3 EAP developer (EAP) releases only. Not using this? See below:
(JIRA 6.2.x documentation | JIRA OnDemand documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

Components are sub-sections of a project. They are used to group issues within a project into smaller parts.

Note that you can set a Default Assignee for a component. This will override the project's default assignee, for issues in that component.

On this page:

Managing a project's components

  1. Log in to JIRA as a project administrator.
  2. Choose > Projects. The Project Summary page is displayed (see Defining a Project).
    (tick) Keyboard shortcut: g + g + start typing project
  3. Choose Components in the left menu. The Components page is displayed, showing a list of components and each component's details. From here you can manage the project's components as described below.


    Screenshot: The 'Components' screen

Adding a new component

  1. The Add Component form is located at the top of the 'Components' screen.
  2. Enter the Name for the component. Optionally enter a Description and select a Component Lead and Default Assignee (see options below).

Selecting a Default Assignee

You can optionally set a Default Assignee for a component. This will override the project's default assignee, for issues in that component.
(info) If an issue has multiple components, and the default assignees of components clash, the assignee will be set to the default assignee of the component that is first alphabetically.

Default Assignee Option

Description

Notes

Project Default

Issues matching this component will have the assignee set to the same default assignee as the parent project.

 

Project Lead

The assignee will be set to the project leader.

If the project leader is not permitted to be assigned to issues in the permission scheme this option will be disabled and will say "Project Lead is not allowed to be assigned issues".

Component Lead

The assignee will be set to the component leader.

If the component leader is not permitted to be assigned to issues in the permission scheme this option will be disabled and will say "Component Lead is not allowed to be assigned issues". The Component Lead option will also not be available if the component does not have a lead assigned to the component. Instead under this option it will say "Component does not have a lead.".

Unassigned

The assignee of the issue will not be set on the creation of this issue.

This option will only be available if "Allow unassigned issues" is enabled in the General Configuration.

Editing a component's details

  1. On the 'Components' screen, hover over the relevant component to display the pencil icon.
  2. Edit the component's Name, Description, Lead and Default Assignee.
  3. Click the Update button to save your changes.

Deleting a component

  1. On the 'Components' screen, hover over the relevant component to display the Delete button.
  2. You will be prompted to associate these issues with another component if you wish.

42 Comments

  1. Anonymous

    is there a way to maintain the compontet with a language dependent name?

  2. Anonymous

    I would really like to be able to version components in the same manner you may version projects.  It would solve many issues for the way we use Jira.  For us, a component is often a piece of hardware or software included in our system project which may change/version throughout the project.  Being able to version the components and record affected component version/s in issues would be a great help.  Adding the same release mechanism to the component would also be helpful.  It would essentially make the component a sub-project but without all the rest of the project details.

    1. Anonymous

      I´m just looking for the same thing. Cannot find anything in the plugins archive. Would be a killer feature!

      I need it for projects where the components are

      - Backend

      - Android App

      - iPhone App

      Would be just perfect to define versions per component, because they have different release cycles. Splitting up the project in multiple projects does not make too much sense.

    2. Component versioning would be a killer addition to the product.  For us, components are often vendor software included in our system projects and not being able to version these components is a major headache.

    3. Anonymous

      +1 to this request. At this point I need independent versioning so badly that I think I'm just going to create one project per component, but the systems are tightly-coupled and as such many issues need to be attached to more than one system. An alternative approach that might be even better is to allow projects to be added as sub-projects of an overarching project, so that issues may be created for one sub-project or for the project as a whole depending on their scope.

      1. Agreed. In our environment JIRA projects should represent software solutions which consist of several components. A solution is just an umbrella but requires a version number independent from its components. Being able to give components version numbers too is crucial for us otherwise we'll have to track each component in a separate JIRA project.

        1. Anonymous

          +1. We really really really really need this.

          1. Anonymous

            Can Atlassian take this up please? It would be really good to group components or tag them.

    4. Anonymous

      Heck Freakin' Yeah!!!! This would be a super sweet feature!!!

  3. Anonymous

    Is there a way of specifying a main Component Lead and his backups?

  4. Anonymous

    Hi All, I'm new on JIRA and testing the possibilities.

    Is there a way to use the same component in 2 different projects ?

    1. Anonymous

      Yes, I believe it is called "Cut and Paste" lol.   But if someone has a better answer, please weigh in!

    2. Anonymous

      No components are project specific and so if you use the name for example User Interface for one project and want to use it for another you can't. As well component names are case insentive meaning just trying to change capitalization (i.e. Component to comPonenT or User Interface to user interface) wont work they are recognized as the same thing in Jira. The better idea is to take some part of the project name and add a dash and then use the component name you wish (i.e. Project 1 - User Interface etc...)

  5. Anonymous

    Will it be possible to track (Burdown) issue completion within a component ?

  6. Anonymous

    How can I make it so that you can create components from an issue? I don't want only admins to be able to create components.

  7. Anonymous

    If i have a issue associated with two components, by default, who the issue will be assigned? The owner of the first component selected? The project lead? Random?

  8. Anonymous

    is there any way to create a component for more than a project at the same time?

     

  9. Anonymous

    how does i managed to set up  one component to point to my repoA and another componenet to point to repoB

    ??

  10. Anonymous

    If I add components to an already existing project will it restructure the project?

  11. As with much of the current documentation relating to OnDemand, the initial instructions don't seem to account for whether or not the "Issues" tab needs to be clicked after choosing "Administration":

    1. Click the 'Administration' link at the top of the screen.
    2. Click 'Projects' and select the project of interest.

    Thus, one needs to click "Issues" after "Administration" to navigate to the indicated screenshots 1 and 2.  Else, one is presented with a set of projects immediately after clicking "Administration," which after selecting a project from that screen will not take you to the project screen with components.

  12. It seems that a lot of folks are asking questions but no one is doing any "answering".....

  13. Anonymous

    I am trying to set up components in the ondemand version of Jira and it does not seem to allow me to do that. Compnents appear as a field when you create an issue, but it is not editable, and when you go to the project summary view, it does not include the components section as described above. Am I doing something wrong?

     

    1. Anonymous

      Ditto.  The documentation indicates that there should be a 'more' on the bottom right of the summary screen, but there is none.  The summary screen for the project only contains Description, Issues: 30 day Summary, and an Activity Stream

      How do I get components to display?

  14. Anonymous

    Hi,

    Is there a way to disable a component from the component list in an issue ?

    Because it can happen that some components are transient, and if I remove it, all issues with this component will be changed (and I don't want).

     

    Thank you

  15. Anonymous

    There description above does not take you to the right project summary page... what you actually need to do is:

    Administration -> Projects -> (your project) -> Issues -> Projects -> (your project)

    yes, it should exist here ------------^^^^^ in its entirety, but doesnt....

  16. Anonymous

    How does one display the component?

    I created a few components; but no field shows up for components when entering the defect.

    I am using the online version of JIRA and working for a verry large French firm with DS as initials; JIRA managers please pay heed.

    1. Anonymous

      I have this same problem. Please help!

    2. Anonymous

      This might already have been resolved, you need to be sure to add the components field to the screen. An easy way to see what's going wrong is when you create a ticket, click on the "Configure Field" button then on "Where's my field?" type in the field you are looking for and it will tell you what's working, what isn't, and where you need to go to fix the problem.

  17. Anonymous

    Is there anyway to add an icon representation for a component?

  18. Anonymous

    Not sure if this is answered somewhere above, but is there a way to get rid of the "No Component" component in Jira? Thanks.

  19. Anonymous

    Whenever I tried to update components it keeps loading but no message or what so ever to indicate error 

  20. Anonymous

    Is there a way to limit component selection to just one component while logging/editing issues? Thanks.

  21. Anonymous

    If you select more than one component and each one has a default assignee, who gets assigned the issue?

     

     

    1. Anonymous

      I beleive it takes the first component alphabetically and uses that assignee.

  22. Anonymous

    Software Developers Develop Software Components, so why cant developers add components to jira, why does it have to be a project administrator, and most baffling, why can't i change this permission? 

    Just over complicated, too many rules. yuck!

  23. Anonymous

    Is there a way to make a group as a lead of the component? The idea would be to receive notifications only for specific component.

  24. I'm trying to use components in a project almost as sub-versions of a product.

    Is there any way to move components (and all the issues within the component) from one project to another?

  25. Anonymous

    What this person said! Trying to do the same thing.

    Anonymous

    Is there a way to make a group as a lead of the component? The idea would be to receive notifications only for specific component.

  26. Anonymous

    is there a way to set some security permissions for each component ? so not each group could only see some specific issues related to that component ?

  27. Anonymous

    To manage modular designs and reuse

    A means to handle composition of components would be essential.

    As would enabling a component to be used in multipl projects.

     

  28. Anonymous

    can this software; atlassian JIRA on demand be used to track staff daily work activity?