Moving issue to a different project is doing nothing Edited

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

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
Community showcase
Published Nov 29, 2018 in Marketplace Apps

How to set up an incident workflow from the VP of Engineering at Sentry

Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...

1,378 views 0 8
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you