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

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 Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,011 views 12 18
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot