Create sub-task post-function bug

Description

*This issue has moved*

This issue has been moved permanently to Adaptavist's Product Support JIRA instance.

All existing users of this instance should have the same username on our Product Support instance. However, you will very likely need to click on the
Can't access your account link in order to reset to a new password.

Hi there, I've noticed a problem with the post-function "Create a Subtask" in new versions of Scriptrunner where it throws errors upon creating a sub-task

Affected JIRA version (that I've tested)

  • JIRA 6.3.10 + Scriptrunner 3.0.10 (Production server)

  • JIRA 6.4.2 + Scriptrunner 3.0.12 (Fresh install)

Scenario
We have a workflow that automatically creates a sub-task when an issue is created. Upon creation of the sub-task, the sub-task will set a different issue security level as a post-function.
This workflow has been working for us for a year or so now until the recent plugin updates.
An error is thrown when creating the parent task, however, the task and sub-task itself is created but not linked. JIRA logs show this error

I've attached the error screenshot and can also attach the full log of the test site if needed.

Notes

  • I thought it was a problem with our workflow so decided to test this with a fresh install of JIRA and Scriptrunner but encountered the same error

  • This error seems to be related to this error another user has GRV-607

  • I've tried removing the "Set Issue Security" post-function in the sub-task's workflow. The same error is thrown in the logs but the issues link properly.

Hopefully I've provided enough information

Environment

Ubuntu server

Activity

Show:
Jamie Echlin
September 9, 2015, 8:52 AM

If you are having the problem:

Error creating issue: Can't transition workflow instance #xxxxxx. Current state is 0, requested state is 1

can you please use GRV-691.

Jamie Echlin
September 9, 2015, 8:43 AM

This is confusing, because the original description of this reported two bugs, one is fixed, and one is I'm not exactly sure.

Jamie Echlin
September 9, 2015, 8:00 AM

There are two different issues in this ticket. The issue as originally described is:

{{ [jira.workflow.postfunctions.CloneIssue] Could not set security level, as the schemes between the two projects are different.}}

And the child subtask doesn't get the security level. This is the same as and was fixed in 3.1.3.

Then there is the issue which is describing which seems completely unrelated, and I'd be grateful if you could raise a different ticket.

- I'm not sure which problem you are referring to.

Mikhail Tuzikov
September 8, 2015, 2:16 PM

We have updated to 4.0.1 and the problem is still here. Only now we need to pay $1250 for it

Is there any more news about this issue?

AlejoA
July 27, 2015, 10:03 AM

We've done some fixes around this issue and I think the next version of SR should be this problem.

Your pinned fields
Click on the next to a field label to start pinning.

Assignee

Jamie Echlin

Reporter

Daniel Wong

Internal Complexity

Unknown

Internal Value

Unknown