Task #2572
closed
Remove VERIFIED Status from Redmine
0%
Description
I'm not sure what effect removing the "VERIFIED" status from Redmine will have, so we should probably check with the plan.io folks and ask them another oddball question.
Regardless of our ability to safely remove the VERIFIED status from Redmine, we can definitely remove the VERIFIED status from Redmine's workflows, by disallowing issues from moving to VERIFIED from any other state.
The docs need to be updated before removing this status.
Updated by semyers about 7 years ago
- Blocked by Task #2565: Update documentation to mention new issue verification fields added
Updated by semyers about 7 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to semyers
Updated by semyers about 7 years ago
- Blocked by deleted (Task #2565: Update documentation to mention new issue verification fields)
Updated by semyers about 7 years ago
- Status changed from ASSIGNED to CLOSED - CURRENTRELEASE
The VERIFIED status has been removed from redmine workflows. It should now be impossible to transition any issue to a VERIFIED state.
After giving it some thought, I think it's not worth pursuing removing this field from Redmine; there's value in preserving the VERIFIED status history for potential auditing later, such as if a flaw in the script I ran in #2566 is later discovered.
The docs also don't need to be updated, since the inability to even set the VERIFIED status combined with the new "Verified" flag, along with the amount of discussion we've had about this on mailing lists, in IRC, and in meetings ought to be good enough. That said, the only docs update outstanding is to the quasi-deprecated build docs for the Pulp release engineer (currently me).
That means this is good to close. :)
Edit: ...forgot to mention that no issues were in the "VERIFIED" state when the workflow change was made, so we don't have to figure out what to do with those.
.