Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,298,418
Community Members
 
Community Events
165
Community Groups

Managing hot fixes

We are using fixVersion for tracking versions. This is fine. However I would like to know what is the best practice for tracking hot fixes etc. For example we have released version 1.0 and we are currently working on version 2.0. We have discovered a bug in 1.0, so we want to make HotFix on version 1.0. One way would be to create version 1.0.0.1 for first hot fix and so on... but then releases page is overpopulated with versions and there are too many versions. Any ideas how to handle this?

1 answer

0 votes

Hi @Damjan Music 

Honestly, I'd do what you recommended - and have sub-versions alongside the main versions.

If this is crowding your releases page - I'd ensure you are marking them as "Released" - so you can filter for Unreleased versions only, making the page cleaner.

Ste

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you