/
How to resolve error occurring when moving plans
How to resolve error occurring when moving plans
Description
This provides some tips on how to work around getting a Plan names must be unique error on the movePlans action. Unfortunately, Bamboo has some unnecessary limitations when moving plans.
Example
0 plans moved out of a total of 20 before a failure occurred. Plan names must be unique
Tip - Finding the plan with a duplicate name
The CLI, by default, moves larger chunks of plans at the same time. This makes it hard to determine what plans have duplicate names. Use the limit parameter to limit the number of plans moved at once. Use –limit 1 and repeat the movePlans request. This will move one plan at a time until it reaches the plan that is causing the difficulty.
Example
-a movePlans --project XXX --toProject YYY --limit 1
Once the plan with the duplicate name is found. Modify its name to something else.
-a updatePlan --plan XXX-PLAN --name "New name"
Related content
moveIssue
moveIssue
More like this
Copy a business scenario from one project space to another using Copy Page Tree
Copy a business scenario from one project space to another using Copy Page Tree
More like this
Handling Advanced Roadmaps for Jira issue links during DC to DC migrations
Handling Advanced Roadmaps for Jira issue links during DC to DC migrations
More like this
Configuration Manager for Jira | Jira Sprint behavior during migrations
Configuration Manager for Jira | Jira Sprint behavior during migrations
More like this
Clone all issues in a project - Data Center
Clone all issues in a project - Data Center
More like this
Bulk clone issues in specific projects
Bulk clone issues in specific projects
More like this