Avoid that an issue gets resolved if time remaining is left on issue?

[Wim Deblauwe]

Hi,

is there a way to avoid that a user resolves an issue if there is still a time estimation left on it? I assume that the Groovy Script Runner can do it, but maybe somebody has already figured out the correct script?

regards,

Wim

[Wim Deblauwe · Accepted solution]

Since I already have the Groovy Runner Script plugin installed. I did it with that. This is the script you need:

issue.estimate == null || issue.estimate == 0

regards,

Wim

[JamieA]

That is useful. But, process-wise, is this correct? I mean sometimes (rarely) I over-estimate the time for the task, and I should still be able to close it. Or do you require that the estimate be changed in that case?

[Colin Goudie]

I would say there's nothing wrong with having the original estimate over estimated but I think wil is referring to setting time left to 0. I.e. If the issue is done then no reason to have time left on it

[Wim Deblauwe]

Colin is correct. It looks at the remaining estimate alone. Or there is no estimate, and that is ok. Or there is a remaining estimate, then it should be 0.

[JamieA]

I got you, thanks

[Andrey Kiyanovsky]

Wim,

can you help me to find the list of all issue parameters useful in Groovy Runner Script, like issue.originalEstimate, issue.estimate, issue.resolution etc...? Thank you in advance.

[Colin Goudie]

You can put custom Condition in the workflow to stop transitions to resolve or closed.

Not sure if this is natively supported now in JIRA 4.3.x or not but I wrote a small plugin to do it ages ago

https://github.com/gommo/Tributech-JIRA-workflows

I think there is another more complete plugin that has these types of conditions. I'll post back if I remember

[Tibor Valy]

You can add a Post Function for the workflow (Close Issue and Resolve Issue in the default workflow). Update Issue Field -> Remaining Estimate = 0.