nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to remove an automatic asignee in bugs

Maria Pinilla

Hello,

I have a question for one of our projects (I took over as admin recently, so did not do the set up). There is a user that gets automatically assigned to bugs. We would like to remove this.

I have checked there are no rules in automation set up, and the workflow has no automatic assignment to her.

How can I remove this default?

Thanks!

Accepted answers

Nic Brough -Adaptavist-

I am sorry that the answer you got before was misleading - it was generated by an AI that has no understanding of your question or Atlassian software.

There are only a couple of places to look for this.

The first is the default/automatic assignee rule in the project.

The project settings have a "default assignee", which can be set to "unassigned" or "project lead". This just sets a default in the assignee field when someone starts to create an issue.

The second is an "automatic" choice, which you can set on a component-by-componet basis to "project default", "unassigned", "project lead", or "component lead"

As you say you have no workflow functions or automations setting this person as the assignee, then it is either a listener or the project settings. Check the project details, and then take a look at the components in the project.

All comments

Pasam Venkateshwarrao

Hi @Maria Pinilla

In the project goto project settings you can see details there you can check whether some one kept default Assignee as a project lead/ unassigned

make that as a unassigned

GNarsimhagowda - Empyra

Hi @Maria Pinilla ,

Try checking if the user is any of the "Component Lead" as this also result in the automatic asignee.

Thanks.

Megha Rajanna

HI @Maria Pinilla

To identify or remove any default assignments causing the behavior, you should check project settings for default assignees, review screen configurations for "Create" or "Edit" screens, verify field configurations for default assignees, examine the configuration for the specific issue type, review user-specific settings or filters, and ensure there are no global default assignees set.

THANK YOU

Nic Brough -Adaptavist-

Please do not use AI to answer questions without checking the answer it gives.

This answer is utterly misleading, talking about irrelevant functions and ones that do not exist.

Nic Brough -Adaptavist-

I am sorry that the answer you got before was misleading - it was generated by an AI that has no understanding of your question or Atlassian software.

There are only a couple of places to look for this.

The first is the default/automatic assignee rule in the project.

The project settings have a "default assignee", which can be set to "unassigned" or "project lead". This just sets a default in the assignee field when someone starts to create an issue.

The second is an "automatic" choice, which you can set on a component-by-componet basis to "project default", "unassigned", "project lead", or "component lead"

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud