nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Add a Validator on a transition screen for originalEstimate?

Timothy Harris

Having some problems validating originalEstimate field in a workflow transition screen.

Using a Validation based on JQL query, which, I believe is provided by the script runner plugin.

The query is simple: "originalEstimate is not EMPTY"

Anybody created validator on a transition screen to require the entry of an Original Estimate?

Accepted answers

JamieA

This won't work if you're trying to do what I think you are, because the issue won't be indexed with the new value until it's committed.

Instead change to a "simple scripted validator", and use the condition:

issue.getOriginalEstimate()

Which is short for

issue.getOriginalEstimate() != null && issue.getOriginalEstimate() != 0

All comments

JamieA

This won't work if you're trying to do what I think you are, because the issue won't be indexed with the new value until it's committed.

Instead change to a "simple scripted validator", and use the condition:

issue.getOriginalEstimate()

Which is short for

issue.getOriginalEstimate() != null && issue.getOriginalEstimate() != 0

Timothy Harris

Jamie, Thank you so much :-) I hadn't thought about the indexing!

Alex Sharp

Recognising that this answer was written a while ago. It appears you now don't need to use Script Runner to perform this validation. You can add this validation directly in a Transition Validator. (Working Jira Cloud ) Transition for Original Estimate.png

danny.shapiro

I saw issues that transitioned with 0m as estimation although we had this validator.
Any ideas why it's happening?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

scriptrunner

jira