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; } } }

Don't assign issue to current user when changing status

EKP

Hello!

I am running into an issue with automatic assignment of the assignee on an issue to the current user when transitioning an issue from To Do status to In Progress status (on a company-managed project).

I've looked into automation rules (project-specific as well as global) - there aren't any rules currently enabled.

I've also checked the workflow transition status "Start Progress" and deleted the following step:

Assign the issue to the current user. Please note that the issue will only be assigned to the current user if the current user has the 'Assignable User' permission.

Still - the issue gets reassigned upon status change.

Is there anyone here who could help me resolve this problem? Thanks in advance!

Accepted answers

Trudy P Claspill

Hello @EKP

Welcome to the Atlassian community.

Each issue type in a project can have its own workflow.

When viewing the Workflow Scheme associated with the project, is there more than one workflow within the Workflow Scheme?

Did you modify the workflow that is associated to the type of issue where you changed the issue status?

All comments

Trudy P Claspill

Hello @EKP

Welcome to the Atlassian community.

Each issue type in a project can have its own workflow.

When viewing the Workflow Scheme associated with the project, is there more than one workflow within the Workflow Scheme?

Did you modify the workflow that is associated to the type of issue where you changed the issue status?

Trudy P Claspill

When you edit a workflow it creates a Draft. After you change the workflow you have to click the Publish button to make the changes take affect. Did you Publish the workflow after changing it?

EKP

Hi @Trudy P Claspill - thanks for getting back so quickly and the warm welcome!

Yes, there's only one workflow scheme associated with this project and it has only one workflow within this scheme.

All issue types (incl. the unassigned ones) in this project are part of this one workflow.

Thanks,

Eva

EKP

There was a delay in loading the comments, and I just saw your second reply: THANK YOU - publishing the draft did it! That was the step I was missing! Really appreciate your help!

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

transition

status

assignee