...
In Step 3 we get to choose the destination project for every issue type in our set of issues.
Bulk Move bug:
...
Don't move sub-tasks with their parent
Things are normal (as above) until we get to sub-tasks, and it all goes wrong:
...
After running the script with unarchive=True, Bulk Move should detect the matching versions and components:
Bulk Move
...
bug: CC field
On the same Step 3 page, you may see a CC field:
The CC field appears if you have the Jira Watcher Field plugin installed:
The Jira Watcher plugin lets you edit the watcher list on regular issue transition screens, as the CC field above. Normally this is what we want, but not during a bulk move.
There is no good option here. If you leave CC blank, your issue watchers will all be lost. If you fill something in, your watchers will be overwritten.
The CC field appears if you have the Jira Watcher Field plugin installed:
Solution: abort the Bulk Move and disable the watcher field for the duration of the bulk move:
...
Bulk Move bug: 'Epic Name is required'
The next problem will may show up in Step 3 when you get to Epics. The bulk move wizard says says Epic Name is required :
What is going on? Well, it's true that for Epics, Epic Name is a required field. But all our moved Epics already have an Epic Name! So why are we being asked for one?
...