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

Tickets are assigned to user when issue is moved from one status to another

Suma Pralhad Kustagi

Hi,

We have a agile board,where in when user moves tickets from To Do to INPROGRESS the tickets are getting assigned to user. I have checked post function and also permission scheme,not able to rectify. Can you please help how to avoid auto assign.

Regards,
Suma

Accepted answers

Gökçe Gürsel {Appfire}

Hi @Suma Pralhad Kustagi ,

Did you check the automation rules for this project and Global Automation rules?

I also suggest checking the other apps installed in your instance.

Regards,

Gökçe

Sagar Mahajan_d8sqh7

Hi @Suma Pralhad Kustagi Can you please check the issue history when issue is assigned to that user when it transition from TO Do to IN PROGRESS status it should show the entry for the assignee change in issue history. as you already confirmed that no postfunction, automation rule.

worth to check issue history to get some hint if any script is created for this.

Nic Brough -Adaptavist-

Jira doesn't do that natively, you have to configure it to do it. So you'll need to turn that off.

Look for:

Post-functions on the workflow transitions that are doing the assignment
Automations
Listeners

All comments

Gökçe Gürsel {Appfire}

Hi @Suma Pralhad Kustagi ,

Did you check the automation rules for this project and Global Automation rules?

I also suggest checking the other apps installed in your instance.

Regards,

Gökçe

Suma Pralhad Kustagi

Hi,

I do not see any automation rules for that project

Sagar Mahajan_d8sqh7

worth to check issue history to get some hint if any script is created for this.

Suma Pralhad Kustagi

Hi Sagar,

Yes I do see in the issue history.

Nic Brough -Adaptavist-

Jira doesn't do that natively, you have to configure it to do it. So you'll need to turn that off.

Look for:

Post-functions on the workflow transitions that are doing the assignment
Automations
Listeners

Suma Pralhad Kustagi

Hi Nic,

Have verified the post function as well listeners, nothing has been specified.Its happening only for a particular project.

Regards,

Suma

Gökçe Gürsel {Appfire}

Who's is the user shown in the issue history making this change?

Sagar Mahajan_d8sqh7

What you see in the history?

Any username like:

User changed the Assignee

User1 -> User2

Nic Brough -Adaptavist-

Ok, let's continue on Sagar's thread above - that's the next step after you've eliminated these.

Suma Pralhad Kustagi

Hi Sagar,

I see that in user history,Assignee has changed from user1 to user2.

Suma Pralhad Kustagi

Hi Sagar,Nic,

I am able to resolve the issue, the issue was with workflow .

THank you for your help.

AKhil kola

hi suma,

i am also getting same error. cloud please help me how to resolve this issue because impacting production.

when reporter has been created ticket right we are moving to another status workflow ticket has been auto assigned to reporter only cloud please confirm issue with workflow or automation rules,

Suma Pralhad Kustagi

@AKhil kola check the workflow the post function there would be automation rule pertaining to assignee because of which the issue occurs.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud