RELATED IDEAS
Ability to set restrictions on tags
As an admin, I would like to set restrictions on tags. For example, to allow integration with external tools, such as Jira, tags can not have spaces. I would like to prevent users from entering spaces in tag names.
An alternative, but somewhat less useful feature would be to prevent non-admin users from creating new tags.
This is a significant impact, since I need to monitor the integrations for failures, then manually re-name tags and manually re-send each item which failed back through the integration.
Not having the ability to integrate Jira "labels" with Aha "tags" prevent us from linking data betwen the 2 systems and can create data mismatches by maitaing the same sort of data in Jira and Aha separately. The workaround proposals that we have receved from Aha team doesn't work for us.
Option 1: Use the Components field in Jira
That field is extensively used to delineate team components and team bounderies, categorize SW components, organize issues in the project, automatically assign people to specific components, tag, reporting, and more. We can't reassign that field to manage Aha "tags", and "components is one of a kind field in Jira. If we need to expand the integration to add additional Aha tags we cannot.
Option 2: Use a pre-defined tags custom field
When we have a list of hundred of tags, having a centralized body to manually manage the tags creates delays and overheads to the business and it's not sustainable.
Proposed Solution
Have the integration to allow substitution characters. It could be configured in the integration as an option - it could also be useful for removing special characters and such.
This makes sense for Jira Integration, since it does not support spaces.