Skip to Main Content
Status Planning to implement
Categories Integrations
Created by Dale Potter
Created on Aug 22, 2024

Allow switching between integration templates if they are integrated with the same project

What is the challenge?

As part of a migration, we are planning to change existing integrations and switch from using "Template A" to "Template B".

The challenge is that "Template B" is not available for selection unless it is integrated with the same Jira or Rally project as the integration (not "Template A"), which it will not be in most cases.

What is the impact?

We are faced with two choices of:

  • Using Template A and manually overriding the mappings (which defeats the point of the template), or

  • Creating a new integration with Template B and manually relinking all the records.

Both of these approaches are not feasible at scale

Describe your idea

Instead of the current validation, which requires that the new template must be integrated with the same project as the integration, could the validation require that the new template must be integrated with the same project as the old template to ensure record types are correctly matched?


  • Attach files
  • Rathishan P
    Reply
    |
    Aug 28, 2024

    The below resolution suggested end up with creation 30 integrations Templates(in Phase1 and going fwd. we may need to add template for each, and every integration exists) and its more of like a normal integration. If the Project in the new template needs to be same as the Jira Project in the existing integration, then what is the point of having new Template. Each workspace is having integration with different Projects. Hope you can understand this.


    Resolution Suggested : -The new integration template needs to be integrated with the same project as the integration you are trying to change the template on - not the same project as the initial template


    So please implement this as early as possible

  • +2