RELATED IDEAS
Make the standard tags field mappable for requirements
Both epics and features have the standard tags field mappable when setting up an integration.
Requirements now have a standard tags field added to the record but it is not available in the mappings. It currently requires a custom field be created to map any tags that are placed on a requirement record.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +2
© 2024 Aha! Labs Inc.•All rights reserved
I ran into the same limitation when trying to integrate Tags from Aha to Azure Devops. It worked perfectly on Epics and Features, but it did not on the Requirement. I would like this to become a feature because it will limit creating a duplicate field.
I also ran into this limitation, last week. I can successfully integrate feature tags to my Jira epic issue type. I would like to integrate requirement tags with my Jira story issues also.
We ran into this today limitation today. Seems a baffling limitation given that tags can be mapped from other record types. Any chance of an admin response as to why the inconsistency?
+1 for this please. I want to integrate tags with Jira but I would need to create a custom field and migrate all existing tags over to make this work.