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 Claspill · Accepted solution]

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.

[Manu Varghese]

Ok thanks Trudy, I will let our team know.

[Marc -Devoteam-]

Hi @Manu Varghese 

This field seems to be related to the 3rd party app Atlas Custom Fields.

So mention this to your admins, that you have an issue with this app field in relation to a native field.

This might be a bug in this 3rd party app. Then you admin should raise this with the vendor.

[Manu Varghese]

Thanks Marc. Our admins have not added an app named "Atlas". I'm guessing it's referring to "Atlassian Atlas", which seems to have migrated to "Atlassian Platform Experiences" (https://community.atlassian.com/forums/Goals-and-Projects-articles/Atlas-is-evolving/ba-p/2686154). There was this mention in a different page (https://support.atlassian.com/platform-experiences/docs/participating-in-the-platform-experiences-early-access-program/):
"As of April 2026, customers can no longer opt our of Platform Experiences. We’re provisioning goals and projects to all Atlassian customers ..."

Is there a group within Atlassian I can contact about this?

[Manu Varghese]

I noticed Trudy's reply just now. Will move the discussion there, thanks.