As part of the Jira to OpenProject migration, resolutions become statuses in OpenProject. The OpenProject Jira importer names each status after the Jira status and resolution (e.g. Closed - Fixed) and reuses an existing status with that name. op.xwiki.org now has Closed - Fixed, Closed - Won't Fix, Closed - Duplicate, Closed - Solved By, Closed - Cannot Reproduce, Closed - Invalid and Closed - Inactive.
To avoid extra statuses, I propose to clean up the few Jira combinations that don’t match them:
Done → Fixed: already done (139 issues), and the Done resolution is removed. Both meant the same thing.
Resolved → Closed: already done (21 TESTREPORT issues). No issue is in the Resolved status anymore.
Incomplete → Invalid: 90 issues (56 in XWIKI, 15 in XE, the rest in 6 other projects), then remove the Incomplete resolution. Both mean the issue can’t be acted on as reported, and having both doesn’t help.
Note that changing the resolution updates the issue’s “updated” date in Jira.
Open question: Reopened. 127 open issues are Reopened (80 in XWIKI). op.xwiki.org has no such status, so the importer would create one. Two options:
Keep a Reopened status in OpenProject: nothing to change in Jira, and it shows at a glance that an earlier fix didn’t work. The workflows would only allow moving a closed work package to Reopened (OpenProject already prevents changing the status of a closed work package whose version is released). It’s one more open status in the workflows and in queries like “status is Open” (queries on “open” statuses in general include it).
Move these issues to Open before the migration: fewer statuses; the reopening stays visible in the issue history.
On question before answering.
Currently in Jira, the ticket status is Open -> Closed -> Reopen, and a ticket can’t go back from Closed to Open.
Would it be the same for OP? Will it be possible to move from Open to Reopen without going through Closed? Or from Closed back to Open?
I never fully understood why we needed a separate “Reopened” status, so I would be in favor of changing to “Open”. It can make sense to have one to “flag” issues we needed to revert, but closing could also simply have been a mistake, so I don’t think “Reopened” currently has a lot of meaning. If we can choose between the two when re-opening an issue, it could make sense to have both, but then we would need to have clear rules what to use when.
Apart from that +1 for the simplification as proposed.
Same as jira, we have full control on the workflow. I don’t think it would make sense to go from Open to Reopened or from Closed - xxx to Open.
PS: We can’t use Reopen since in jira it’s called Reopened and thus all issues would be imported with Reopened , but we can probably rename it to Reopen after the import is finished.
Yes I think I agree with you that it would be too complex and not worth it (and misused). I’m fine with dropping “Reopened” in jira (note that we’ll need to configure a new Reopened → Open transition before doing a bulk change, but that’s not hard).
Incomplete → Invalid (90 issues), and the Incomplete resolution is removed.
Reopened dropped: the 127 Reopened issues are now Open, and it’s no longer possible to transition an issue to Reopened: “Reopen Issue” now moves it back to Open. The reopening stays in each issue’s history.
Every Jira status/resolution combination now matches an OpenProject status, so the migration won’t create any extra ones. In OpenProject, reopening a closed work package will mean moving it back to Open.