RELATED IDEAS
Allow use of Mapped fields template with one field difference for each integration
What is the challenge? |
Can't use Mapping Integration template. Have to update multiple integration for every mapping change since one has to be different. |
What is the impact? |
Would save a ton of time for our team. |
Describe your idea |
We have around 20 product ADO integrations all using the same integration template. We also have the Product Name fields which is a required field on creation and has a different value for each product/integration. This means that we're unable to use the mapping template since we have to customize a single field for each integration. This means that all common changes need to be done under each of the integrations separately. This gets quite tedious. It would be great if we can use the common template for all mapped values except one. This would allow us to just edit the template once for any change and keep each integration updating the right Product Name on creation. |
-
-
-
- +1
© 2025 Aha! Labs Inc.•All rights reserved
I like this idea, but I would take it further. We're similar in all the ADO is under 1 project. There are several fields I want consistent and sever I want to make unique for each integration. The current mapping option is all follow the template or none. I'd prefer to see it at that level AND at each record AND at the field. That way if say all my feature records are consistent I can leave that section controlled by the template. But then my user story/requirements level I could make unique down to the individual field.