Component lead isn't assigned

[André]

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é

[Bharat Kalia · Accepted solution]

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

[André]

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.

[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é]

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

[André]

I have checked, but there's no option through the servicedesk portal to set an assignee. I'll have a look in Jira now if I create there directly, but I might need to have a look at how servicedesk works in that regard and if this is defined in a workflow or something.

[André]

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 service management and regular jira I guess. In regular Jira I also get the assignee choice and it's on automatic by default.

[Bharat Kalia]

@André - Maybe you need to go and check on the request type? If the assignee is given default value there and hidden you might never be able to catch it. I might be here but just thinking out of the box..If creating a ticket directly from "Create" button works, most likely there is something been set when submitting via portal.

Hope this resolves soon.

Thanks,

Bharat

[André]

Hey @Bharat Kalia , I found a solution, but I feel it's kind of a workaround. I put a post-function on create in which I set assignee to automatic and then it assigns it to the component lead. If anyone has any idea on how I could change jira servicemanagement in a way so it won't screw up the assignment I'd be interested, because now when someone creates an issue and assigns it specifically it will get overwritten, but normally that doesn't happen in this project.

[André]

@Bharat KaliaI didn't know what you meant, but I found it and you were right! So if you click on a request type you see which fields are used and there are hidden fields in there. With us someone set the assignee to a specific user, which botched my attempt to assign it to someone else.

Thanks alot for helping out! And of course also @Sahir Maharaj 

Kind regards,

André

[Bharat Kalia]

@André ah I should have posted a "Screenshot" but glad you found it :) 

[Sahir Maharaj]

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é]

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.

[André]

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.