Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your Jira Software Cloud company-managed projects to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
A guide on how to deploy and monitor an application built on AWS using Atlassian and third-party tools.
This page is for company-managed projects
If the lower-left of your project sidebar says you're in a team-managed project, check out these team-managed project articles instead.
Learn more about the difference between company-managed and team-managed projects.
Components are subsections of a project. They are used to group issues within a project into smaller parts. For example, teams may use components to group issues that describe work on specific data objects, services, plug-ins, or APIs within their project.
You can set a default assignee for a component. This will override the project's default assignee, for issues in that component.
Only project admins and Jira admins can manage components.
You can access Components, from your project's sidebar.
The Components page allows you to add, edit or delete components in your project. For each component in your project, the following details will be displayed:
Add a new component
To add a new component:
Navigate to Components in your project’s sidebar. Select Create component.
Give the component a meaningful name.
It's a good idea to give a description to the component. Component descriptions appear as a tooltip when a user hovers their mouse over a component label.
Optionally, set a component lead. This is usually the team lead responsible for overseeing work associated with the component.
Optionally, set a default assignee for issues created with the component.
When you add components to your project, a new Component field will appear in the More fields panel of your project’s issues, allowing you to set a component on an issue. You can also import issues in bulk via More () > Import issues from CSV.
Select a default assignee
A component default assignee will override the project's overall default assignee. If someone creates an issue with more than one component, and the default assignees for those components are different people, then Jira assigns the issue to the default assignee of the component that was created in the system first.
You can nominate an individual person by searching for their name.
If your project's team changes frequently, you can set the default assignee to a particular role. This can future-proof the default assignee of a component, in the case that someone leaves your project. Here's the available options:
Project default - if someone creates an issue with this component, assign the issue to the same person as the project's default assignee. Learn more about project default assignees.
Project lead - if someone creates an issue with this component, assign the issue to project's lead. Learn more about project leads.
Component lead - if someone creates an issue with this component, assign the issue to component's lead.
Unassigned - if your site allows unassigned issues and someone creates an issue with this component, the issue will remain unassigned.
Edit or delete a component
In the component's entry on the table, select More (•••).
Select Edit or Delete.
Was this helpful?