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:
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? |
Hi, Team any update on this? This was agreed to complete in August - September time frame
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