You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
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.
Back in April of last year one of the major product announcements from Opsgenie was the launch of the Incident investigation view which created a deep connection between Bitbucket and Opsgenie, empow...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.