Unable to clone when using a ScriptRunner database field with ClonePlus

Description

We have added a database field using the ScriptRunner add-on, and since then we are no longer able to clone issues with ClonePlus. We still can use the standard clone and it works correctly, but not with ClonePlus.

Environment

None

Activity

Show:
Nishanth Thimmareddy (Bob Swift Atlassian Apps)
September 28, 2020, 12:48 PM

Apologies for the inconvenience, , we haven’t been able to get to this in the last month and now, we have prioritized this. You should see updates rolling in the coming week as we analyse this in detail.

Regards,

Nishanth T

Darren McElfresh
October 7, 2020, 1:41 PM

Any updates yet?

Ravi Varma (Bob Swift Atlassian Apps)
October 9, 2020, 11:13 AM

Hi ,

We reproduced this issue with the following combinations, where it was working for some combinations and breaking for others

JiraVersion

ScriptRunnerVersion

JCPP version

Status

7.13

6.5.0

6.6.0

Working

7.13

6.5.0

6.7.0

Working

8.0.3

6.5.0-p5

6.6.0

Working

8.0.3

6.5.0-p5

6.7.0

Working

8.0.3

6.6.0

6.6.0

Not Working

8.4.3

6.5.0-p5

6.6.0

Working

8.4.3

6.5.0-p5

6.7.0

Working

8.4.3

6.6.0

6.6.0

Not Working

8.4.3

6.10.0

6.6.0

Not Working

8.8.1

6.5.0-p5

6.6.0

Working

8.8.1

6.5.0-p5

6.7.0

Working

8.8.1

6.6.0

6.6.0

Not Working

8.8.1

6.10.0

6.6.0

Not Working

8.8.1

6.10.0

6.7.0

Not Working

8.11.1

6.5.0-p5

6.6.0

Working

8.11.1

6.5.0-p5

6.7.0

Working

8.11.1

6.6.0

6.6.0

Not Working.ScriptRunner not compatible

8.11.1

6.6.0

6.7.0

Not Working.ScriptRunner not compatible

8.12.1

6.5.0-p5

6.6.0

Working but ScriptRunner not compatible

8.12.1

6.5.0-p5

6.7.0

Working but ScriptRunner not compatible

8.12.1

6.6.0

6.6.0

Not Working.ScriptRunner not compatible

8.12.1

6.6.0

6.7.0

Not Working.ScriptRunner not compatible

8.12.1

6.10.0

6.6.0

Not Working

8.12.1

6.10.0

6.7.0

Not Working

Following are the observations:

  • ScriptRunner v6.6.0 and above has this issue

  • ScriptRunner v6.5.0-p5 is working perfectly with JCPP v6.6.0 and v6.7.0

  • Based on the error stack trace shared with us, IssueParametersCapturingImmutableCustomField.validateParams() is thrown by the underlying implementation (by ScriptRunner)

  • ScriptRunner team is working on this vide SRJIRA-4688. Though SRJIRA-4688 is related to IssuePicker field, once addressed, should also fix DatabaseField issue as well. Both fields throw same underlying error IssueParametersCapturingImmutableCustomField.validateParams()

  • You should be able to verify, once ScriptRunner releases v6.11.0.

Please confirm, if the issue is addressed in ScriptRunner 6.11.0 or not.

Regards,
Ravi Varma

Darren McElfresh
October 9, 2020, 12:20 PM

Great! Thanks you!

Ravi Varma (Bob Swift Atlassian Apps)
October 12, 2020, 8:55 AM

Hi ,

We have verified that this issue is resolved in the latest version (v6.11.0) of ScriptRunner. Hence resolving this issue. Please verify the same at your end.

Please reopen, in case you are able to reproduce the issue.

Thanks,
Ravi Varma

Assignee

Ravi Varma (Bob Swift Atlassian Apps)

Reporter

Darren McElfresh

Labels

None

Support Entitlement

SEN-12319698

Story Points

1

Time tracking

0m

Sprint

None

Priority

Major
Configure