why groovyrunner executes the clone and link post function without stop?

Tsol
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 16, 2012

Hi everybody,

i'm using clones an issue and links postfuction in create transition in order to create a related issue.

The problem that occurs is that postfunction doesn't terminate it's execution and as a result creates the same issue hundred times and after that JIRA crushes down.

You can see the order of the post functions in the attached file.

Plugin's version is: 2.0.6

JIRA version is: 4.4

Any idea of what's going on?

Thanks,

Kostas

1 answer

1 accepted

2 votes
Answer accepted
JamieA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 16, 2012

You create an issue. The post-function creates another issue and links it. The issue that's created also has it's post-functions invoked. Therefore you get a never-ending chain of issues.

If you want to create another issue that has the exact same workflow, and you want an issue cloned on the create step, you need to put in some condition such that it's only true for the human-generated issue.

If you log.debug the values of transientvars and args, you should find something that you could use for the condition.

Tsol
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 16, 2012

Thanx a lot. It was a terrible mistake.

JamieA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 18, 2012

Not really ;-)

Presumably you were testing on a dev instance so you didn't take down your production jira...

Suggest an answer

Log in or Sign up to answer