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 Pahax Henry 13 days ago

Hello,
To solve this workflow issue in your project management tool (like Jira), you can use the following approach:

Custom Scripted Workflow Condition: Implement a custom condition in the workflow that checks if the total spent time is less than or equal to the total estimate before allowing a status transition or assignee change. You can achieve this using ScriptRunner or similar tools in Jira.

Restrict Time Tracking: Use Permission Schemes to control which users can log time on specific issue types (e.g., enabling time tracking only for Stories but not Tasks).

Automation Rule: Create an automation rule that triggers when the time is logged and compares the spent vs estimated time. Notify or block the assignee change if the condition isn't met.

These steps should help enforce your process and prevent forgotten steps.

Best regards,
Pahax Henry

(1-1/1)

Project

General

Profile

Redmine