Jira Best Practices

[Bunty]

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.

[Matt Doar · Accepted solution]

I think I'd keep one project with multiple versions

[Bunty]

Thank you for the reply @Gonchik Tsymzhitov @Matt Doar

[Gonchik Tsymzhitov · Accepted solution]

Hi! 

How do you planning of your work?

Which methodology or combine of methodologies do you using?

Also, have you using burndown charts? Have you trying to do retro after improvements of your work. 

Unfortunately, to my understand, you can not find a silver bullet. Otherwise, why in the world a lot methodologies :) 

Let's start to check this one:

https://www.atlassian.com/customers

https://community.atlassian.com/t5/Jira-articles/Best-Practices-Strategies-for-Defining-your-JIRA-Projects/ba-p/603061

Also, it will be good if you provide more detail info: 

1. Industry

2. Service/product orientied company or just outsource

3. Capacity 

4. Release cycle

5. QA

6. Which tool do you using for plan? 

7. Most reason the problem from retro feedback? 

Cheers,

Gonchik Tsymzhitov