Aha Admin team is looking for a way to not hack the system by tracking custom fields used in AHA to Jira Integrations.
Currently, the Admin team is adding a J* to the custom field name for each custom field with a Jira in the Name, API Key, Description, Used in Products or Used in Layouts. Aha users without Admin rights can not see all the data linked to a custom field.
If Jira is not used in the custom field Name, API Key, or Used in Layout, it is difficult to identify a custom field linked to Jira Integration. See example.
Aha has limited sorting Search and Sorting in the custom field page (Only 4 columns). We would like to propose adding the Internal Name in the "Add Custom Field Page.
With the change by adding Internal Name column in custom fields search and sort capability, J* can be removed from the Name and reloaded to the Internal Name. It is known that the J* or Jira identifier is loaded to the Name and description, but only Admin users can see this. Without the Internal Name column added to the CF page, it will cause limited viewing by internal Admin users only, limiting sort and search capabilities for view level users.
This request is important and needed for AOP, and strategic planning. We are trying to reduce adding new fields and increasing reusing currently used custom fields.
Aha usage is increasing quickly with the potential of adding between 5,000 to 20,000 new users in the next few years. It would be instrumental to have this capability sooner than later.
See Attached file for clarity in Custom Field capabilities and needs.