Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Pull request status before merge and review timeout

José Antonio Martínez Iglesias
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 10, 2023


We would like our pull requests to be reviewed in a 2 phase secuencial process:

1. Developers review

2. QA review

Also, we would like to establish a duration for each phase (a number of days), so that when that timeout is reached an action can be triggered (as sending email or notifications to some users).

I have been reading about "Tasks", "Checks" and "Review status", and we are already using that functionallities in our projects, but I can figure out how to use them to implement the described flow in a suitable way, so that we can manage/filter PRs in each state etc.

Thanks a lot!

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events