The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation trigger when code committed to the associated branch

Kamal Mustafa
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!
March 13, 2020

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

Comments for this post are closed

Community moderators have prevented the ability to post new comments.

Zoryana Bohutska _SaaSJet_
Atlassian Partner
April 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

TAGS
AUG Leaders

Atlassian Community Events