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,459,132
Community Members
 
Community Events
176
Community Groups

Enforcing SDLC SLA for Pull Requests

Edited

Hello and thank you for your time,

We would like to track and enforce DB schema reviews covered in our SLAs for when DEV commits PRs until DBA gives an "Approve", "Deny", or "Needs Work" for the PR in Bitbucket.

I have seen that Jira Service Desk allows for setting SLA for Jira work tickets, but didn't know if there was a way of enforcing our SLA with automated alerts inside Bitbucket or if we can integrate with Opsgenie or another in the Atlassian stack.

Currently looking at  sending payloads from Bitbucket -> Opsgenie

Opsgenie receives payload and suppresses alert until SLA time has been exceeded.

Attempting to Auto-close PR-Opsgenie-alerts when associated PR:Approved|PR:Denied|PR:NeedsWork payload is sent from Bitbucket -> Opsgenie

 

Example of desired process:

DEV commits PR

SLA starts

1 hour passes - no response from DBA schema reviewers

SLA alert is created for DBA reviewers.

 

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events