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.
I love the potential of leveraging Bitbucket repos to aide in Incident root cause analysis but it currently assumes the latest commits relate to a given deployment. This doesn't work for teams which host multiple client environments, deployed from multiple versioned artifacts.
To follow the current approach, we'd need a way to take in the following information for a given deployment/environment Service:
I realize things like this isn't easy and takes time. Does anyone have intermediate ideas that go to the spirit of this functionality?
Hi @Adam Benfer -
Sounds like instead of seeing "Commits added" in the Opsgenie incident investigation, you would rather have "Artifact versions added", or at least something that correlates to that. Is that correct? I understand that this would help pinpoint the artifact releases that were potential causes to an incident rather than commits that don't necessarily relate to the release.
Although I can't think of any workaround that would work for this use case, I'd be happy to open up a feature request for this if you'd like.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.