Moving issue to a different project is doing nothing

invinci June 21, 2017

We just moved to JIRA 7.0.11 from 6.3.1 and already started to see issues to our workflow setup. I am trying to change project type for an existing issue and the process does not take in all the mappings. For every project change that I try to do, it stops at the screeen where I need to enter the Componenet/s field value. 

Jira_Behaviors_Issue_0.jpg

As a workaround, turning off the behaviors will allow me to make the move successfully.

Below are the errors and debug statements of moving the issue on JIRA;

Jira_Behaviors_Issue.jpg

I would like to know if there is any way to validate the behaviors in the production instance of JIRA? Do I need to change any configuration on the serverside script of behaviors?

Thank You!

1 answer

0 votes
Jamie Echlin _ScriptRunner - The Adaptavist Group_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
June 21, 2017

We are dealing with this as a support request, when the resolution is found we'll update here.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events