I search solution to control that total estimate not less than total spent

There is my workflow: when total spent of Story became more than total estimate, we need to stop and re-evaluate the Story. When i control it by myself, there is no problem. But when i try to delegate this process to devs or qa, there are situations, where flow had been forgotten.

I want solution like this: dev added track with time in Story, and when he try to change assignee, he can't do it until total estimate <= total spent. At least, until estimate <= spent, without subtasks: i will change the flow and we will not use subtasks for tracking.

There are second problem, that i can't limit ability to track devs to issue by tracker: for example, they can track only in Story, but can in Task. or vice versa

Replies (1)

RE: I search solution to control that total estimate not less than total spent - Added by Eva Mason about 4 hours ago

To streamline your workflow and ensure that Stories are re-evaluated when the total time spent exceeds the estimate, you can implement the following solutions:

1. Enforce Estimate Validation:
Custom Script or Automation: Use a custom script or automation rule in your project management tool to prevent changing the assignee if the total spent time exceeds the estimate. This can be done using tools like Jira Automation, where you can set conditions to check time spent and compare it to the estimate before allowing changes.

2. Time Tracking Constraints:
Permissions and Roles: Set up permissions to restrict time tracking to specific issue types (e.g., Stories only). This can help ensure that developers and QA members only log time against the Stories and not against Tasks or other issue types.

Custom Workflows: Modify the workflow to include validation steps that check the total spent time against the estimate and prevent transitions (like changing the assignee) if the conditions are not met.

Implementing in Jira:
Automation Rule Example: Create an automation rule in Jira that runs when the assignee is changed. Add a condition to check if the total spent time is less than or equal to the estimate. If the condition fails, set an action to block the change and display an error message https://www.litebluelite.com

Permissions Configuration: Go to project settings and configure permissions to restrict who can log time and on which issue types.

Simplified Steps:
Create an Automation Rule to prevent assignee changes if spent time > estimate.

Set Permissions to restrict time tracking to Stories only.

Modify Workflows to include validation checks for time spent versus estimate.

(1-1/1)

Project

General

Profile

Redmine