RELATED IDEAS
Ability to copy/move an integration template
We would like to be able to copy and move an integration template from one workspace to another. This would allow us to restrict access on the template if we could move it to a location that no regular users have access to. We can then use that template for any new integrations while keeping it in a secure location.
-
ADMIN RESPONSEJul 10, 2020
Thanks for the idea!
We do not have any plans on our roadmap at this time to support this idea. However, we will continue to monitor for community feedback.
© 2024 Aha! Labs Inc.•All rights reserved
We discovered an edge-case where the integration template was in a workspace which had been inadvertently archived (because it had no other content) and then the ability to use it as a template stopped.
The ability to copy and save a template as an updated version would be an excellent feature to have. Especially for those who have revisions and want to modify multiple integrations at the same time (instead of doing it one by one).
We're on a mission to clean-up and make administrative changes easier across 70 workspace. We already have a template that serves 55 of them - it would be great to able to copy and move it, since our IT department now restricts access to the service account we use between Aha & Jira. We can no longer login with it, so we end up creating requests for them to do Aha administrative work. This results in writing instructions & how-tos for things we could easily do ourselves.
If we could copy & move templates, we could remove technical debt in the system for ourselves that inhibits our ability to innovate quicker.
We have certainly seen the need to move an integation template in the hierarchy.