Behaviours Issue Type mapping doesn't work correct

Case: We have behaviour mapped to IssueType A and Project1. When the Create Issue screen is loaded and I chose the IssueType A the default values filled correct. Then if I chose another issue type (IssueType B) loaded default values do not remove from fields.

I found issue with similar problem (but with the Project field):

JIRA version: 7.1.2

ScriptRunner version:

1 answer

1 accepted

This widget could not be displayed.

Looks it's correct bevahiour until you have mapping for issuetype B and initializer function filled.

Try to create mapping for B and Project11 and update initializer function with purging instructions.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

165 views 1 3
Join discussion

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