GIVEN
A user has selected a saved backlog and is presented with the associated migration view
WHEN
The user enters their github credential (they must have write access on all of the source repos), creates a list of target repos and performs a gesture on an affordance to migrate the tickets
THEN
On each of the target repos, the issues will be migrated over, a new project will be created that is named after the saved backlog, 4 Columns will be created in that project (Backlog, To Do, Ready For Testing, Done), and cards will be added to the Backlog column in the order they were specified in the groomed backlog saved to the application
GIVEN
A user has begun migrating tickets
WHEN
The user is waiting during the long automation process
THEN
The user will be presented with something to signify that the process is ongoing
GIVEN:
The user has migrated the tickets
WHEN:
The process is complete
THEN:
The user will be redirected to a view that signifies successful migration
GIVEN
A user has selected a saved backlog and is presented with the associated migration view
WHEN
The user enters their github credential (they must have write access on all of the source repos), creates a list of target repos and performs a gesture on an affordance to migrate the tickets
THEN
On each of the target repos, the issues will be migrated over, a new project will be created that is named after the saved backlog, 4 Columns will be created in that project (Backlog, To Do, Ready For Testing, Done), and cards will be added to the Backlog column in the order they were specified in the groomed backlog saved to the application
GIVEN
A user has begun migrating tickets
WHEN
The user is waiting during the long automation process
THEN
The user will be presented with something to signify that the process is ongoing
GIVEN:
The user has migrated the tickets
WHEN:
The process is complete
THEN:
The user will be redirected to a view that signifies successful migration