nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can I remove a component lead?

Captain Kirby

I'm setting up a project that includes a range of components. I added a person to the "component lead" field when creating some components. That was a mistake and I want to remove the person from the component lead field (I don't want any user assigned as a component lead.) However, I can't find a way to do that. I can change the component lead to someone else, but not to "unassigned" or delete the person in the field. I know it's possible since several other components I have set up have no component lead, and that's just fine.

Accepted answers

Bill Sheboy

Hi @Captain Kirby -- Welcome to the Atlassian Community!

There is an open defect for this symptom, which you may vote for / watch to see progress: https://jira.atlassian.com/browse/JRACLOUD-93602

There is a workaround noted, but it requires calling the REST API endpoint. That could be done with a standalone API tool, a custom app, or an automation rule.

Kind regards,
Bill

All comments

Dexter de Vera

Hi @Captain Kirby ,

Welcome to the Atlassian community!

No need to change the component lead, you can just set the default assignee base on component to unassigned so it will be automatically set to unassigned when you add a component. Component 》[...]

The changes will be executed to newly created issues (after updating the component default assignee)

Note: make sure there is no Jira automation related in assigning user.

Check this documentation for more information about managing component: managing-components-and-default-assignee-selection-in-jira-software-projects

Hope it helps,

Thanks!

Prachi Bolar

hello,

Welcome to community

Please check this article : https://support.atlassian.com/jira-software-cloud/docs/configure-jira-components/

Fill out the new component’s information.
1. The name is used in a work item’s Components field, and when searching for component in the project.
2. The description appears next to the component on the Components page, and helps people understand what it represents.
3. The component lead is the person responsible for overseeing work related to the component.
4. The default assignee is the person automatically assigned to new work items that include the component.
  1. The project default assignee is the person who confirms that reported work items are meant for their team, and who re-assigns them accordingly.
  2. The project lead assignee is the person who controls and manages a project's settings. This person is defined in the project settings.
  3. The component lead assignee is the person responsible for overseeing work related to the component. This person is defined in the Component lead field.
  4. If the component stays unassigned, new work items that include this component aren’t assigned to anyone.
Select Save.

Thank you,

Prachi

Bill Sheboy

Hi @Captain Kirby -- Welcome to the Atlassian Community!

There is an open defect for this symptom, which you may vote for / watch to see progress: https://jira.atlassian.com/browse/JRACLOUD-93602

There is a workaround noted, but it requires calling the REST API endpoint. That could be done with a standalone API tool, a custom app, or an automation rule.

Kind regards,
Bill

Captain Kirby

Thanks Bill! Appreciate you pointing me to this. I commented and voted for it as well.

Captain Kirby

I appreciate your response. Functionally, it's not a problem. However, leaving a name in the lead field causes a documentation error for team members arriving at the project. Your point is valid, and I do appreciate it.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud