Why am I automatically assigned to all new issues ?

[Raphaël NORYNBERG]

Hi everyone,

I'm the project lead of every project, on our Jira instance, but the field "Default assignee" is set to "Unassigned" on each project.

I even add a Post Functions rule that says "The value of field Assignee will be cleared." after the 1st rule "Creates the issue originally.".

But despite of that, I'm always automatically assigned on each issue...

I precise that none of the creation screens contains the field "Assignee".

Could someone help me and tell me what I'm missing ?

Thanks in advance for your help !

[Raphaël NORYNBERG · Accepted solution]

Hi everyone, 

I have succeed to solve this problem myself !
For those who are interested, I missed one place where we can set a default assignee : Components.
On my instance people who creates issue must complete the "Component" field, and on my projects each components pointed at the "Project Lead" to be the default assignee, that's explains why I found myself assignee on specific issue type, because on the other issue types there is no component field to complete on creation.

Thanks again @Fabio Racobaldo _Herzum_ and @Frederik Vantroys , you helped me clear the possibilities ! 

[Stephen Harman]

Components!  I was losing my mind.

[Frederik Vantroys]

when you go to project settings /details you can see the project lead and the dropdown below should be set to unassigned in your case:

Also possible that it is a post function inside your workflow that assigns you when an issue goes from one state to another (but not very likely)

Or automation ? 

[Raphaël NORYNBERG]

No, each leads you mentioned before hase been covered :

- The field "Default assignee" is set to "Unassigned" on each project.

- It only happens on New created issue (and I even add a Post Functions rule that says "The value of field Assignee will be cleared." after the 1st rule "Creates the issue originally.")

- No automation rules

The only one that remained open was that "default assignee set for that issue type", but I understand you have confused it with the project field right ?

Thanks anyway

[Fabio Racobaldo _Herzum_]

Hey @Raphaël NORYNBERG , please check if there is some post function at create - workflow level.

[Raphaël NORYNBERG]

Hi @Fabio Racobaldo _Herzum_ !
Thanks for this answer.

As I said : "I even add a Post Functions rule that says "The value of field Assignee will be cleared." after the 1st rule "Creates the issue originally.""

[Frederik Vantroys]

This can happen on a few different levels ...

- Default Assignee: There might be a default assignee configured for the project or issue type you are working with. When a new issue is created, Jira automatically assigns it to the default assignee set for that project or issue type.

- Workflow Configuration: Jira workflows can be configured to assign issues automatically to certain users or roles at specific workflow transition points. For example, when an issue transitions from "Open" to "In Progress," it can be set to automatically assign to the current user or a specific role.

- Automation Rules: Jira provides automation features where you can create rules to perform certain actions based on predefined triggers. It's possible that there is an automation rule set up to assign new issues to you or to a specific user or group.

- Permission Scheme: The permission scheme for the project might grant you the "Assignable User" permission. This permission allows you to be automatically assigned to new issues created within that project.

[Raphaël NORYNBERG]

Hi @Frederik Vantroys 

Thanks for your answer !

Could you tell me where did you find a setting that set a default assignee to an issue type please ?

It could be that.