Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

"Quick" Move Issue to a New Project

Does anyone know of an extension or other means of quickly moving individual issues from one project to another?

I know how to move an issue, but the series of steps is daunting when I simply want to keep the type, status, etc, and just move it to the new project.

1 answer

1 accepted

6 votes
Answer accepted

I'm not aware of anything.

It does seem like an "easy request" to "just move" issues around. But the devil is definitely in these details.

Jira does simplify the steps when it realizes there are one-to-one mappings. But the "Move" process is defined to allow for the complicated situations, collapsing to rote click-thru for the simple cases.

Be sure to use "Bulk Move" if you have more than one or two. So there are already two different ways to move issues between projects. Inventing yet another way isn't likely.

Just for fun, I experimented with a cross-project Board to see if the any of the views would allow me to drag issues between projects. No joy there. I wasn't even able to "reparent" issues this way.

A few parting related thoughts:

  • If the root problem is that issues are being created in the wrong project, encourage your users to double-check the "Project" field at the top of the "Create Issue" screen. I don't know why it's wrong sometimes, but even I screw this up on occasion.
  • If you have just one, or a small number, of "move use-cases", you could create automation rules for each move destination. Not sure it saves many clicks, but it may be a simpler approach, especially if folks already know how to manually invoke Jira automation rules from within an issue.

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

221 views 2 1
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you