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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

What is the best way to transition from an old to new Jira project environment?

We've been using Jira for years. 

Our current feature request backlog has almost 1,000 items in it now :(

On a side note, we're also considering trying out Jira Product Discovery, so we can better track our backlogged feature requests. 

What is the best way forward?

Should we create a new project in Jira and start fresh? 

But, in that case - what happens if we have a new user request for the same item we have on our old backlog (but not in our new project environment)? Do we apply a vote to it, and then just keep pulling from these old tickets into our new project environment over time? 

OR, should we spend the time upfront, and go through the 1,000 tickets over the next few months, and tag the majority of them as super long-term, so they are off our active backlog via a filter of some sort? In this case, we (don't) start a new project. 

Any suggestions are appreciated! 

1 answer

1 accepted

0 votes
Answer accepted
Riley Venable (Atlas Bench)
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 04, 2023

There are a couple of options that you can consider. One option is to create a new project and start with a fresh backlog. However, this might result in duplicating items that are already in your old backlog. A better option might be to prioritize the backlog and tag long-term items as such so that they can be filtered out of the active backlog. This approach could save you time in the long run and help you to focus on the most important items. Additionally, you might want to consider using Jira Product Discovery to help you better track your backlog and prioritize items. Ultimately, the best approach will depend on your specific needs and goals.

Thanks Riley - appreciate the thoughts! 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events