Hello All,
I was wondering if anyone had Jira best practices with the following concept.
Each of our teams are focused in a specific technology area or layer for code that goes the code base for our switch products. This means that for each software release we get tasked with 1 or more requests. Sometimes these requests are for support of a new feature or capability. Sometimes these requests are for enhancements, defect reduction or quality improvements. We regularly get unexpected or unplanned work. How do you structure/create projects that can handle a never-ending stream of issues without also creating an unwieldy amount of historical information?
The pattern we have been following is that for each software release we will create a new Jira project. For items that we were tracking in the previous project, I can move them to the new one now that they are going to be delivered in the next software release. These allow us a way to go back and see what we delivered specifically during a set time window. Within each project, we’ll have different Epics to cover the main areas where we have issues or stories that need tracked and worked on. Each new project will carry over a couple common Epics as well as have new ones for the new major requests that my team gets.
Is there another pattern that can be followed that might be better than what we are doing?
Thanks in Advance,
Mani.
