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

Automation trigger when code committed to the associated branch

One common problem we're facing, dev forget to update issue status from Open to In Progress, even though they already started working on the issue. This mean the duration from In Progress started to Resolved never true. If there's trigger for the first commit on branch associated with the issue, we can automatically transition the issue from Open to In Progress.

1 comment

Zoryana Bohutska _SaaSJet_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Apr 15, 2020

Hi @Kamal Mustafa 

You can try custom triggers at the add-on SLA Time and Report.

This app lets you configure SLA Timer with flexible start/stop/pause conditions: (status, assignee, issue type, summary etc.) and with automate action for exceeded issue (notification, changing reporter, priority or status).

Please let me know will it help you


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events