Currently, I'm trying to define two conditions regarding the component field in a subtask:the field should be required --> I realized this requirement setting the specific option in the corresponding field configuration. Everything fine.the field should only contain one component, not more and not less than one...I tried to define a behaviour with respect to the specific project and field. I was successfull in checking the amount of components in the specific subtask and to send a user message or an invalid input message.Now my question: When I'm entering two components in the edit dialogue the behaviour fires, but jira updates the issue (what I wanted to avoid) although the behaviour throws the exception.Here is the snapshot of my behaviour code:def issueManager = ComponentAccessor.getIssueManager()def issue = issueManager.getIssueObject("ITP-25")def NumberComponents = issue.getComponents().size()log.debug "NumberComponents: " +NumberComponentsif (NumberComponents != 1){ throw new InvalidInputException("component", "Only one component is allowed") return null}I tried some alternatives, e.g. "return false" or throwing the invalidInputException without the assignment to the field...but nothing helps. Thus, I assume I'm not on the right track...Has someone an idea? Thanks a lot in advance!

Community
Q&A
Jira
Questions
Scriptrunner - Behaiviour: how to stop updating an issue because of an specific condition

Quisiera saber si es posible bloquear una incidencia para que no se pueda mover si no esta estimada

Ejemplo: tengo una tarea que esta activa en el sprint en curso y se encuentra en estimación , deseo que no la puedan mover a por ejemplo: estado en curso si no se completo primero la estimación inicial de dicha tarea. Es decir que sea bloqueante el campo de estimación inicial, si no se completa no es posible mover la incidencia a otro estado.

Quedo al aguardo.

1 answer

1 accepted

0 votes

Answer accepted

Hi @Günter Halmans

Have you tried

somefield.setError("Only one component is allowed")

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

No, I'm going to try it in a few minutes :-)

what kind of object is "somefield"?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

the field you would like the error message to show against - maybe the Components field would work, not sure

your code will also have to clearError() when the condition is clear

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Tom,

it works! Thanks a lot - You have saved some painfull hours of my time :-)

best regards,

Günter

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

Quisiera saber si es posible bloquear una incidencia para que no se pueda mover si no esta estimada

1 answer

1 accepted

Suggest an answer

Was this helpful?

Thanks!

TAGS

Community showcase

Atlassian Community Events