How parallel sprints are managed by the Configuration Manager for Jira app on instances with different configurations

 Use Case

Given two different Jira instances, one with “Parallel Sprints” enabled and another one without, how does the Configuration Manager for Jira app manage the deployment of these sprints?

 Test using Configuration Manager for Jira

To determine the behavior, the following procedure was followed:

1. Create a test project on an instance where “Parallel Sprints” are enabled (Sprint 1 and Sprint 2).

2. Create a “Project with Issues” snapshot and deploy it on the target (the instance without “Parallel Sprints” enabled).

Open

3. The project is deployed as a new one and one can verify that both the sprints are still active on the target.

Open