We do CSV imports to JIRA
new JIRA values for the field are can be created on the fly - is there a way to prevent this ? even for jira-administrators ?
If not specified in your CSV file, imported issues will be given the default (i.e. first) Priority as specified in your JIRA system Defining priority field values. You can also create new JIRA values on-the-fly during the import process.
Not really. As a jira-adminstrator (assuming System Admin rights), the only defense against creating new values is making sure the csv file is properly formatted. Also using the "Map Field Values" function is what I would call the Last Chance to get it right.
Now, a workaround you could use would be to log in as a normal user (with Project Admin rights) and do the import through the project administration screen. When doing an import, new values can only be created based on your user access level to JIRA. If you don't have JIRA administrator rights, you can't create new values on a system field like Priority.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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!
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