Project lead not getting assigned to issues

[Deleted user]

When creating an issue, we´ve set it so that the project lead gets assigned to the issue automatically. Recently it gets assigned to one of our administrators and not the project lead.

What needs to be done so that the "Spoc" gets automatically (without automation seetings) assigned to the issues?

Thank you in advance!

[Lyanh Hoon · Accepted solution]

I have the same issue in Jira Service Management.  There's no component set up or post-function to auto-assign issues.  @[deleted] Were you able to find where the problem was that you could share?  

[Deleted user]

Hi @Lyanh Hoon

yes the Jira support was able to help me through it.

The problem was that in the "request types" one user was set as Assignee (dont ask me how, I didnt do it)

So when you check request type, there will be a hidden assigned field and if that has a present value with the user name you just have to remove him/her so that the next created issues will be assigned to the project lead.

Hope I could help you :)

[Lyanh Hoon]

@[deleted]Thanks for sharing. Yes, I was able to find that there's an assignee field in the Request Type set automatically by Jira that caused the issue.

Thank you!

[Deleted user]

I´m glad I could help, you´re very welcome <3

[Daniel Ebers]

Hi @[deleted]

is there any chance the component setting of default assignee is overriding your settings - to check could you check if there are components set to the troubling issues in question and if so, if there are settings for components which could be responsible?

https://confluence.atlassian.com/adminjiraserver/managing-components-938847187.html

I am assuming so because:

Components are sub-sections of a project. They are used to group issues within a project into smaller parts. You can set a default assignee for a component. This will override the project's default assignee, for issues in that component.

Regards,
Daniel

[Deleted user]

Hi @Daniel Ebers thank you for your reply!

actually on ALL projects there were automatically given those two components by jira servicedesk (we didnt create any other). And all are assigned to the project default.

Regards!

[Daniel Ebers]

So - just for a summary and a better understanding, you still see some other user than "SPOC" assigned when a Component like "Öffentliche Website" is selected, is this right?

If so and no setting via component lead + no setting via project default is taking place + no setting via workflow is done - only some sort of automation, possible via an App comes to mind.

[Deleted user]

Do you mean to solve the problem via automation setting or to check if automation is set?

[Daniel Ebers]

I would recommend to check first.

[Deleted user]

No on all our projects we dont use automations.

It´s the same project where we had this problem that the user/customer couldnt see its own tickets: https://community.atlassian.com/t5/Jira-Core-Server-questions/User-has-no-access-after-creating-a-ticket/qaq-p/1689098#M56762

We figured out it was a bug in the workflow by copying and pasting the exact same workflow from another project to project 2 and the problem was simply solved. We thought the Project lead "bug" would also be solved by copy/paste the same workflow but the problem still lasts

[Daniel Ebers]

Ah, I see - so it is more a collection of suspicious things. Well, in case they are dependend on each other (or even if not) maybe something in configuration (but to be honest then I cannot imagine where that should be) or you are hitting a series of bugs (not likely, but who knows).

I would in your case investigate further which administrator is set to the issue - if there is some pattern. If it is every time the (same wrong) account and such.

[Niranjan]

Hi ,

Check the workflow post-function of Create Issue transition.

If the issue has component field value, check the components page in the project(if issues with components has default assignee)

[Deleted user]

I´ve checked the field configuration scheme (which is the same as in other projects) but in that project there doesnt occur this problem with the project lead