Advice Needed -Tracking Developer Time against tickets & automation to notify PM when getting close?

Wendy Grapentine

Also curious what other people use as well.

Situation:
PM's input hours into Original Time Estimate Field in Jira. 
Developers log their hours against tickets using Jira Add-On called TimeTracker. 

Complications:
- Time Tracker works great against the direct ticket.  It can not aggregate or roll-time up to a parent ticket. 

Request from PM's - Create a Jira automation that will notify the PM's and the Sales Reps when actual developer time logged is 80% of the Original Estimated Time has elapsed.  

Notifications themselves should not be a problem. Question is more to do with:
1) how would I set up automation query
2) how would your company do something like this?  Any recommendations?

(Sorry if nebulous, need help with # 1 and just curious on #2 if there are better/different ways to track dev time)

Amit Bansal_mz9tfs

Issue 1 - Complications:
- Time Tracker works great against the direct ticket.  It can not aggregate or roll-time up to a parent ticket. 

Approach - Time tracking should be done against sub-tasks (under all stories/tasks/bugs) so that they roll up to parent ticket. You can write an automation rule to trigger updation of estimation field of parent story/task as soon as subtask estimation is updated.

Post which you can use workratio field to check if it has reached 80.

 

Issue 2 - 

Notifications themselves should not be a problem. Question is more to do with:
1) how would I set up automation query
2) how would your company do something like this?  Any recommendations?

 

Approach - 

1) Step 1

- Automation rule for updation of estimation field when any subtask sees change in estimation field.

- Automation rule for slack/email notification as soon as story/task has workratio >-=80

 

2) We don't have any such requirement. Also, I am not sure how this alert would be used by the receiver.