Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Pan/prepare my "delivery packages".

Hi Jira community!

I want through Jira to plan/prepare my "delivery packages".

These packages are agreements that the team makes to understand what are the features that we will include in the next release. It is not a sprint backlog because we operate with a continuous flow/delivery (pulled system).

I realized that some colleagues do this through a release. That is, they understand what the next package is and all issues receive the same release name.

The question is: As we do not know in advance what the exact version name will be, would it be a good practice to name a version of, for example "Next-package release", and in the future, adjust this name (to the real name, for example 2021-04-15) before the release?

1 answer

That is exactly what we do.

We create a release named something like "Next Release". As code makes it through the CI cycle we have the developers set the JIRA issue Fix Version to "Next Release". Then when we are ready to deploy the accumulated fixes we change the release name from "Next Release" to the version number we have decided to apply to the package, and then we create another Release entity named "Next Release".

In that manner, everything that was set to Fix Version="Next Release" automatically shows the new name of that release when we update the Release Name. And for the developers they don't have to worry about what the next release's actual version number is; they know the process is always to simply set the Fix Version to "Next Release"

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Confluence

⚡️NEW Group for Confluence Cloud Admins

Calling all Confluence Cloud Admins!  We created a new Community Group to support your unique needs as Confluence admins. This is a group where you can ask questions, access resou...

113 views 2 9
Read article

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