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; } } }

Cannot set Default Assignee to Component Lead

Kenneth McCarthy

Hi,

With a newly created Kanban board we wish to utilise the Component field to automatically assign jira tickets to the Component Lead. Unfortunately it is defaulted to Project Lead and I cannot change it. I have administrator permissions and have tried everything we know, even the project lead cannot unassign himself from this and we have searched/tried all options that were suggested in similar posts. Would really appreciate any assistance on this.

Accepted answers

All comments

Max Foerster - K15t

Hi Kenneth,

so you're saying that you have the Administer Projects permission in the project the component belongs to and you can't edit the component in the project settings?

Best, Max

Kenneth McCarthy

Hi Max,

Correct regarding permissions but I can edit the component and component leads in the project. It is that I cannot get the default assignee to be the component lead with a jira ticket is created. The default assignee is the Project lead and I cannot change that to be the component lead.

Regards,

Kenneth

Fazila Ashraf

Hi @Kenneth McCarthy

Suggest you to look at your project's permission scheme. Especially, on who has the 'Assign issues' and 'Assignable user' permission.

Max Foerster - K15t

Hi Kenneth,

when you create the issue the assignee is set to "automatic"? Because components should and will always overwrite the default assignee of the project.

Kenneth McCarthy

Hi Max, yes correct, it is set to automatic. Once the jira is created it is though automatically assigned to the Project lead

Kenneth McCarthy

Hi Fazila,

Yes we have looked at the permissions and the appropriate permissions are set for us, which makes this all the more confusing to resolve.

Max Foerster - K15t

Okay, that sounds strange unfortunately. Next thing I'd like to try is, can you guide step by step through everything you do? And maybe please add a screenshot of the component configuration? Which version are you running on? Do you use any apps that could interfere with the auto-assignment? Any workflow post-functions maybe? The easiest thing to test would be. Create a new blank project please, set up a component with the default assignee and try to reproduce the behaviour.

Nabil

Based on all the comments so far, Max does have a point. It does seem that there is a workflow post function assigning the tickets.

If it is a Service Desk project, see the Request Type fields as well just in case there is an Assignee field hidden with a preset value.