What is the challenge? |
When I create an integration template, it is based on a workspace integration that I put in place. If I make changes to that workspace integration, it adjusts the template. My challenge is that I would like to create a template that contains a base number of fields, and then add custom fields for each project. But sometimes, I want to make a new field part of the overall template. With the current mechanism, I have to go back and update every integration. |
What is the impact? |
We have over 20 integrations based on one template, so it is quite cumbersome to update. |
Describe your idea |
I would like to see an integration template that can be created in a generic way and doesn't have to a workspace. It would be ideal to select 'save integration as template' and then have that integration template be editable independent of any specific workspace, rather than having it tied to a specific workspace (and also being able to rename that template). Outcome: That would make managing integrations much less cumbersome. |
please merge with this idea: https://big.ideas.aha.io/ideas/A-I-18151
We found a workaround by cloning the integration and calling the one that we use as temple "Do not touch"
Not sure if that is the most elegant way to handle this but it works for now