Problem Definition

Currently in JIRA, users can create duplicate custom fields. This is a problem because if a user creates a custom field with the same name as a default JIRA field and adds it to screens, it can make reporting in JIRA and in Portfolio inaccurate. An example field is Story Points. A user could create any number of Story Points fields and associate them with screens, but Portfolio will only read the field with the default field ID and thus, Story Points will not populate in Portfolio.

Duplicate fields can also cause other issues and confusion for site administrators.

Suggested Solution

Prevent users from creating duplicate custom fields or at the very least display warning messages about custom fields being created with the same name as default JIRA fields.

An issue could arise where this solution would prevent users from importing projects because their projects have the same field name as a field already in existence in the destination instance. This could be worked around by renaming those fields in the source instance.