(JIRA)Ticket assigned to wrong project after creation


One of our users has shown me an issue , that he's been having in JIRA.Bellow is the situation with fictional project keys.

In the create issue screen he chooses the project ABCD, fills all the details neccesary for it to be processed. He hits create, and suddenly it occurs, that the ticket has been created not in ABCD, but LKBV, before hitting create he has ABCD in the project field. I advised him for the time being to migrate such issues to the proper project via the bulk change=>move function.

Is there any way to check why does this happen, also what needs to be done to get rid of this problem? Is it fixable at all, for me as a jira admin?

Thanks in advance for your help.

Best Regards,

Slawomir Ziolkowski

1 answer

1 accepted

0 votes
Accepted answer

Sounds like you've got something that automatically moves the issue.

Start with a quick look at the issue history - look at the first two changes on the issue, what exactly do they say? Change of project or not?

Then have a look at the listeners and post-functions you've got in the workflow.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,660 views 18 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you