How to set assignee to issue based on Component Lead

[Massimo Grilli]

I know that there are other similar posts, but I haven't find any satisfactory answer in them.

I have created a set of components with the component lead as the default assignee. My expectation is that the component lead should be automatically set as the issue's assignee  when the relevant component has been chosen by the creator.

However, the issue remains unassigned. Is there anything else that should be configured on my JIRA project to enable this feature?

Thanks for your help!

KR,

Massimo

[Max Foerster - K15t]

Hi Massimo,

could you please make sure that the component lead as a user has the "Assignable User" project permission in that project? That'd be my first guess. So just try to assign the issue manually to the user. And are you adding multiple components where not all components have a component lead?

Best, Max

[Massimo Grilli]

Hi Max,

Thanks for your reply.

yes, the each component lead is part of a group that has the "Assignable User" permissions on projects. In fact, I can manually assign them issues.

To keep it simple, I have assigned the issue just to one component, but it doesn't work.

Any other ideas?

Thanks,

Massimo

[Max Foerster - K15t]

Oh, wait for a second Massimo. So you add a component to an already existing issue? That won't work. The auto-assignment only works when the assignee is set to "automatic". That triggers the logic which will go through the order settings of the project - project default - default lead of added components - assignee field.

And when you create an issue the assignee field is set to "automatic" by default. :)

Does that answer your initial question?

Best, Max

[Massimo Grilli]

Hi Max,

no, that was not the case. I had the same problem also creating a new issue. I checked and all configuration about permissions and default assignee were ok, according to your suggestions.

I solved the problem creating a post function in my workflow at issue creation: assign to component lead developer. Now it works as expected.

Thank you very much for your support, it helped me in finding the solution.

KR,

M.

[Max Foerster - K15t]

Hi Massimo,

as it seems to be a viable solution for you at the moment to use a post function I would encourage you to further look into this and maybe reach out to the Atlassian support. I never came across this behavior before and if this is happening in your whole instance that's a serious issue. Have you ever checked the log files for related error messages? And you're welcome. :)

Best, Max