Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Issue Type switches from Defect to Story when moving issue to new Project

David Speight
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Oct 16, 2023

When I move a Defect between Projects, when I select the New Project the New Issue Type switches from Defect to Story. This is OK when user notices and corrects, but unfortunately most don't, any fix planned? I'm using Jira v9.10.1 

1 answer

0 votes
Mykenna Cepek
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 16, 2023

You could search here (Jira Software / Server / Suggestions) to see if this feature has been suggested, and if so, vote for that change. That's worth doing, but don't hold your breath waiting for it to be fixed. They have a LOT in their backlog.

_ _ _ _ _ _ _

Another option to help avoid user error in this use-case would be to create a Jira automation rule which does it correctly each time. Unfortunately, there isn't a rule action to move an issue from one project to another. So if you're ok with a workaround...

The automation rule I'm suggesting would start with the "Manual trigger". This means users would select the rule name from the "More" or "..." menus on the specific issue. So naming the rule well is important, to allow your users to find and select it (perhaps something like "Move to XYZ" where XYZ is the destination project).

The rule would then use the "Clone issue" action to make a new issue in the destination project. This is also an opportunity to customize the "Summary" if you want, using Smart Values.

Finally the rule would close the original issue ("Transition issue" to Status "Done"). You could optionally add a comment including a link to the cloned issue.

If you're new to Jira automation, you could start here:

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events