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!
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?
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.
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.
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
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.