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

Component lead isn't assigned

André_or9czx

Hello,

I'm trying to set up the simple/basic component lead assignment in a servicedesk project in Jira. First I tried with automations (as chatgpt made me believe this would work) but it didn't and then decided to just use the built-in functionality for it. I have set the component lead on one of our component and created an issue only with that component, but it doesn't assign it.

I've already looked at these things:

- I am not updating the issue, I am creating it (as we want it to work)

- I have checked if the user has assignable user permission (they do)

- I have checked if there are any automations still running (even legacy ones), there's no modern automations, there are some legacy ones, but they don't change the assignee.

- I have checked the default assignee for the project, it was not set, I set it to the project lead, as all other issues which can't be determined from the component, should go to that user.

I am at a loss (and so is chatgpt) on where it's going wrong.

We use atlassian cloud with jira and jira servicedesk management.

Does anyone have any idea where this might still go awry?

Thanks in advance for any help you can give me!

Kind regards,

André

Accepted answers

Bharat Kalia

Hi @André - Welcome to the Atlassian Community. Can you please confirm what is your Component Default Assignee? Please make sure "default assignee" is Component lead if you want to use "Component lead" as the option.

Would you mind putting in a screenshot here if you go edit your component?

Thanks,

Bharat

All comments

Bharat Kalia

Would you mind putting in a screenshot here if you go edit your component?

Thanks,

Bharat

Sahir Maharaj_28wu8p

Hello @André

From my experience, the built-in component lead assignment should work if all configurations are correct.

Double-check that the component lead has the necessary permissions, and ensure no conflicting automation rules override this functionality.

P.S. Testing with a different project or a new component might also reveal the root cause.

André_or9czx

Here you go, I put in both the component and the project setting. I think I'll follow up on the other suggestion and try in a different project and different component.

André_or9czx

As mentioned, I think I have checked all that you are mentioning. But I will try it in another project and/or with a new component, that might give some more insight in where to look indeed. I'll post here when I know more.

Bharat Kalia

Hi @André - I think when creating the issue you might have to leave the assignee field as "automatic". Can you please check if that is being followed. The screenshot looks correct and here is the doc for ref - https://confluence.atlassian.com/jirakb/managing-components-and-default-assignee-selection-in-jira-software-projects-1385105793.html

Thanks,

André_or9czx

Ah very sharp, I'll go have a look right now.

André_or9czx

So I tried creating an issue from Jira directly (rather then via the servicedesk portal) and then it works fine, so it's something between jira servicedesk and regular jira I guess. In regular Jira I also get the assignee choice and it's on automatic by default.

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-service-management-cloud

jira-service-management