Project

Profile

Help

Task #2564

closed

Add new fields to Redmine to track issue verification

Added by semyers over 5 years ago. Updated over 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

This was discussed on pulp-dev: https://www.redhat.com/archives/pulp-dev/2017-January/msg00018.html

This task is concerned with creating Redmine fields to track whether or not an issue requires verification, as well as whether or not that issue has been verified.


Related issues

Blocks Pulp - Task #2565: Update documentation to mention new issue verification fieldsCLOSED - CURRENTRELEASEsemyers

Actions
Blocks Pulp - Issue #2566: Retroactively set "Verified" flag on issuesCLOSED - CURRENTRELEASEsemyersActions
Actions #1

Updated by semyers over 5 years ago

  • Blocks Task #2565: Update documentation to mention new issue verification fields added
Actions #2

Updated by semyers over 5 years ago

  • Related to Issue #2566: Retroactively set "Verified" flag on issues added
Actions #3

Updated by semyers over 5 years ago

  • Related to deleted (Issue #2566: Retroactively set "Verified" flag on issues)
Actions #4

Updated by semyers over 5 years ago

  • Blocks Issue #2566: Retroactively set "Verified" flag on issues added
Actions #5

Updated by semyers over 5 years ago

  • Status changed from ASSIGNED to CLOSED - CURRENTRELEASE

I've added the fields. In the email chain, we discussed "Requires QE Verification" as a field name, but I thought "Verification Required" was a little simpler, and more clearly indicates its relationship with the "Verified" field.

Actions #6

Updated by bmbouter over 5 years ago

That name does sound better. Thanks @smyers!

Actions #7

Updated by semyers over 5 years ago

I added this field to the Story and Issue trackers at first, and then put it to the team whether or not we should also add Task and Refactor. We generally agree that these flags are unlikely to be used, but still may be desired, particularly given the risk of regression with refactors and the variability of tasks. So, I've enabled these status flags on all trackers.

Actions #8

Updated by bmbouter over 3 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF