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

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,461,016
Community Members
 
Community Events
176
Community Groups

CI/CD Ticket Tracking Best Practices

Hi everyone! My company is switching to CI/CD and a corresponding weekly release, and I am unsure of the best way to track tickets.  I'm looking for recommendations on how to track each team's tickets, specifically around the following questions:

1. Do you use fixVersions, Due Dates, other? 

2. How do you keep supporting departments (e.g. Production Support) informed on what's getting released and when?  

3. If you have any "hotfixes" (changes that break from the scheduled releases) do you use a separate mechanism for tracking those?

4. What else do you recommend as a Best Practice? 

Note: we are using CircleCI to manage our pipelines.  

Thank you everyone for your support and input! 

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events