Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

I Want to confine User to use Epic if its LoE should be more than 40 Hrs

I have to configure Epic in a way so that if its total Level of Effort needed is less than 40 hrs ,then it should not allow User to create Epic in JIRA Software.

Is ther any way we can put a check on this or some validation soit allows USer to submit Epic when its LoE is greater than 40 Hrs.

2 answers

Hi @Ambrish Dwivedi 

What problem you are trying to solve by enforcing that test on level of effort (LOE)?

This seems more like a knowledge and education issue for people creating the issues, explaining how you are using epics and other issue types, and how to size LOE, rather than a Jira enforcement issue.

Or perhaps it is a work intake challenge, where people are asked to estimate LOE in hours.  Are the people creating these epics doing the work to deliver them?  If not, why would the epic-creator be estimating in effort hours, rather than something coarser like sizes: small, medium, large, or unknown?  Then allow the team to validate that forecast at refinement before start of work.

Best regards,

Bill

0 votes

Hello @Ambrish Dwivedi

Thank you for reaching out.

Unfortunately, there are no workflow validators that can require a specific time estimation to be set in a Jira issue in order to create it. We have a feature request created to implement this improvement:

Transition Validator to check if a field has a valid value 

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

As a workaround today, you can try one of the following options:

1 - Create an automation rule that will close the ticket if it has less than 40 hours of estimation:

Screen Shot 2020-12-15 at 20.18.32.png

This will not prevent the issue creation but will prevent the issue from being counted in your reports and let the user know why it was closed.

2 - Use a third-party app, as Jira Workflow Toolbox 

Let us know if you have any questions.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,104 views 8 28
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you