Custom field called "Project" clashes with system field - can I disable the custom field?

Manu Varghese

Starting Friday (May 29th), the REST query for issue creation metadata for the "Bug" issue type in our project started returning _two_ fields named "project".

our-url/rest/api/3/issue/createmeta?projectKeys=our-project-key&issuetypeIds=bug-type-id

....
            "project": {
              "required": true,
              "schema": {
                "type": "project",
                "system": "project"
              },
              "name": "Project",
....
....
            "customfield_12958": {
              "required": false,
              "schema": {
                "type": "atlas-project",
                "custom": "com.atlassian.jira.plugin.system.customfieldtypes:atlas-project",
                "customId": 12958
              },
              "name": "Project",
              "key": "customfield_12958",

This is causing an error in an internal tool that assumes that field names are unique. As far as we can see, we have not added a custom field named "Project" on our end.

Do you know if this is something that was rolled out to our site on Friday? Is there a way to disable that second field?

Trudy P Claspill

Hello @Manu Varghese 

That custom field type came from the Atlassian product formerly known as Atlas. That Atlas brand has been sunset and the features are being incorporated into Platform Experience.

https://community.atlassian.com/forums/Goals-and-Projects-articles/Everything-you-need-to-know-for-the-upcoming-Atlas-to-platform/ba-p/2941803

In addition the Jira system Project field nomenclature in the UI has been changed to Spaces, but the underlying field name has not been changed yet as that would impact numerous APIs and integrations as well potentially wreaking havoc with other features.

Given that both are Locked fields you cannot actually remove either one. And based on my Google searches it is not possible to disable the Platform Experience features (i.e. Projects and Goals).

My recommendation is that you enhance your internal tool to be able to distinguish between the two fields and to be capable of dealing fields that have identical names, as Jira has no limitation to require field names to be unique.