How to limit giving original estimates for sub-tasks?

Gopi.K August 22, 2022

How to limit giving original estimates for sub-tasks?

eg: allow not more than 2 hours for sub-tasks

1 answer

0 votes
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 23, 2022

Hello @Gopi_K

Thank you for reaching out.

I'm afraid Jira Server does not have a validator that would prevent time tracking fields from receiving a determined value.

I believe the best option would be to use Jira automation to properly add a comment in the issue informing that an invalid value was added to the field. Optionally, you can also use Jira automation to properly transition the issue to an "Invalid status" and require the user to set a value < 2h to proceed in the workflow. These would be the steps:

  1. Ensure you have the Jira automation app on your Server site
  2. Configure a new status to move the issue to when the original estimate is more than 2h. Allow any status to transition to this one
  3. Navigate to your project > Project settings > Automation
  4. Configure an automation rule using the logic of the one below:
    1. Issue trigger: Issue is updated
    2. If: Issue type is sub-task
    3. If: Original estimate > 2h
    4. Action: Add comment
    5. Action: Transition the issue to an invalid status
      Screen Shot 2022-08-23 at 2.40.17 PM.png

Doing the steps above, the issue will be transitioned to the invalid status and a comment will be triggered every time the Original Estimate field is more than 2h, not allowing the issue to proceed in the workflow.

You can check the documentation below for more details about Jira automation:

Jira automation - Data Center and Server 

Let us know if you have any questions.

Suggest an answer

Log in or Sign up to answer