Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

What's a good practice when managing a small/frequent release process?

Edited

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.

0 comments

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events