Custom field import issue - if custom field is associated to one issue type and is mandatory


We have created several issue types in JIRA. We have created many custom fields, but not necessarily will be used by all issue types. To do that, we have associated the custom field to the required issue types in field configuration.

But, after doing that while importing any issue type, this field is not shown in the import wizard. So, we changed the association to any work item type in field configuration. This enables the field to be in the import wizard and allows us to import the issue type data with that field.

But, this has created another problem. The custom field is required for all work item types, but now while creating other requirement types, we are getting error. The error states that the custom field should have some value.

Please let me know how well we can manage that.



1 answer

1 accepted

Accepted Answer
0 votes

This was resolved by making all the customfields global and then creating a field configuration for each issue type and then customizing the field behavior in field configurations.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted yesterday in Featured Groups

Tuesday tips & tricks: What is the Atlassian Community?

It's officially Tuesday, which means it's officially time for another tip to help you better navigate this space we call the Atlassian Community. 😄 I got a great question from community member, Sa...

26 views 0 3
View post

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