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.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Back in 2010 I hadn't been using the Atlassian tools (JIRA, Confluence, Bamboo) that long and I started searching online to see if I could chat to other users primarily about how they used the produc...
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!
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