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 Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Tuesday in Jira

Tell us how your team runs on Jira!

Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...

190 views 1 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