Placeholder for small Projects Without version

[Apurva Deshmukh]

Dear Jira Community,

We are currently in the process of transitioning from our recently released major product version to the development of the next version. In this transitional phase, we've identified the need for a solution to manage small projects (like high availability, Backward Combability ) that arise between these two releases.

The challenge we are facing is that these small projects don't quite fit into the context of the upcoming major version. Adding them there would likely lead to confusion and difficulty in tracking them effectively within the scope of that version. Therefore, we are seeking suggestions and advice from the community on how best to handle these small projects.

We are looking for a suitable placeholder or mechanism within Jira that allows us to keep track of these projects without cluttering the roadmap for the upcoming version. Our goal is to ensure these projects receive the attention they deserve while maintaining a clear and organized workflow for the main development track.

If anyone has faced a similar situation or has insights into how to efficiently manage such small projects in between major versions, we would greatly appreciate your input. Your experiences and ideas could be instrumental in helping us make informed decisions on how to proceed.

[Judd Garratt - Path of Trees]

Some other ideas if your projects don't have a 1-1 mapping with release/deployment version in Jira:

• Create an epic for each small project (which can then be assigned to a release as needed)
• Create a separate sprint or sprints that only contain issues for a specific small project (see parallel sprints)
• Give issues/epics for each small project a specific label or component and then filter them out of the timeline view
• If you're using Advanced Roadmaps with an issue level above epic (e.g. 'legend'), you could group each small project as a 'legend' to keep it seperate from the main release

Good luck!

[Logi Helgu]

Why not just create a new FixVersion?

If you have the "RecentlyReleasedMajorVersion" and "NextMajorVersion" then create new fix version for those "minorRelease"(s) to track what's in them ;) Could also name the last major 1.0.0, and the next major 2.0.0 and then you can have all the 1.X.X to improve the first major :)