d14e44e4ca55 , I completely get it!

The last thing I want is to have to licence a bazzillion plugins for basic functionality enhancements. I suspect the ones they do implement have just had more noise made about them than this one. I'd love to see the size of the current wishlist

+1 me for no plugin & make this tiny change LOL

LOL. Atlassian.  Where tickets are opened 20+ years ago and still ignored. 

Hi

I agree with Heidi. this is a very important feature. You added the option to add custom field at customer and organization level.. but not at very high level as Project..
Add-on are fine but they are not free considering the cost of the cloud subscription.. I believe we must have this feature
regards

Hi,

If you are ok with a 3rd party app, our Software Configuration Management Toolkit app allows you to associate custom attributes for projects, versions and components. You can use these attributes in your JQL queries and GraphQL. 

Regards,

Deniz

Enterprise customers have a need to have multiple ways to categorise projects. There may be a requirement to create hiearchies, represent that a Project belongs to a certain part of the business, represent how the project has been built.

This information also then needs to be available in Atlassian Analytics for reporting purposes. Plugins are understandable, but the data is not necessarily available in Atlassian Analytics.

Having custom project fields provides both flexibility for large organisations, and the data for reporting purposes.

We are aware of Project metadata, but these fields are not easily accessible or editable by Project Admins.

Flexibility and data-driven is our approach, and we hope that Atlassian will consider working on this particular piece of work. Thank you.

This issue highlights Atlassian's blatant disregard for our needs. Your consistent negligence speaks volumes about how you value your customers. Thanks for nothing.

I agree 100% with @Nate Whitehead.

Having this functionality supported by more than 800 users for for 20 years on the demand list and then still ignoring it is nothing but bullsh!tting the community. It just shows that even voting for required functionality is a waste of the community's time.

If Atlassian is intentionally choosing not to implement this simple feature that's been outstanding since 11/Nov/2003 4:26 AM (original creation of the first issue I can find on the topic) - 21 years - can we have a justification on this standing and close out the issue? Just saying "you can do that with forge or a plugin" is a lame answer. Issues have custom fields you can add on to. Needing to pay extra either in the way of a plugin or developing an extension is ridiculous. The community has showed this is something we've needed for over 20 years - this is not a sign of listening to the customer. Either tell us no and stand behind it or commit and build it - cut the bull shit.

We would like to add a custom field to the project detail settings to reference an internal ID.

We need link the Jira project with our information systems with APIs. The pivot variable, to create this link, is an internal ID.

We would like to have a global vision about our projets in a central dashboard : how many issues, evolutions, tickets, service request for a project and to create this dashboard we need to have this internal ID in the properties of a Jira project.

We avoid to put this ID in the name or in the description of the project.