public class TestUpgradeMakingIssuesActiveInOsworkflowFinalState
extends BaseJiraWebTest
Test checks if after running upgrade task issues that were previously in osworkflow final state (state without outgoing transitions)
can be transitioned to new state (after adding 2 new final states and linking existing final state to 2 new final states)
Previous workflow ----done
Altered workflow ----done----new state1
\---new state2
TEST-12 issue created by JIM in final state (done). By default JIM adds entry in OS_CURRENTSTEP for all entries.
TEST-14 issue created normally and transitioned to final state (done). No initial entry in OS_CURRENTSTEP
TEST-17 issue created normally and bulk transitioned to final state (Done). No initial entry in OS_CURRENTSTEP
TEST-19 issue created normally and transitioned to done. Then finish date set to null in OS_HISTORYSTEP for that issue. Upgrade task should not process this issue.
TEST-20 issue created normally and transitioned to done. Then removed one top record from OS_HISTORYSTEP_PREV to mimic double entry in OS_HISTORYSTEP that should be resolved by ordering by finish date.
SEC-2 issue created by JIM in final state (done) and then bulk moved to other project with different workflow.
By default JIM adds entry in OS_CURRENTSTEP for all entries. Also changing workflow creates new entry in OS_CURRENTSTEP even in final state
SEC-4 issue created normally and transitioned to final state (done), then bulk moved to new project and workflow. No initial entry in OS_CURRENTSTEP
SEC-5 issue created normally in second project and transitioned to final state
- Since:
- v7.3