You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
We have recently been aiming to deploy features to production in small and frequent deploys. Ideally one ticket at a time, but due to timing and resource constraints, deploys can include 2 or 3 tickets at a time, depending on what is ready. We work in 2 week sprints and deploy as often as possible.
I wold like to track releases, grouping together the tickets that were deployed at the same time and was intending on using releases for this. It seems to me that releases are aimed at planning larger releases. Are there any good/common practices for our deploy goals?
Thanks,
Colin.