You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
We have a current live project that has maintenance issues (bug fixes small enhancements) and we are going to rewrite that project with newer technologies from scratch. Should this be a new project in Jira? What is a good way to organize or differentiate projects?
I'd say it sounds like a good case for a new project. But it very much depends on how you want to run your teams and project work.
I would be tempted to leave the current project open for maintenance fixes, and have a new project for the rewrite, as it's probably a separate bigger peice of work.
I doubt the people doing the maintenance really care about the replacement when they're trying to support the old system, and I doubt the developers really want the support noise which applies only to something they're replacing.
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.