Actions
Issue #3005
closed
redmine_bugzilla script restores NEEDSINFO flag on developer after it has been removed
Status:
CLOSED - NOTABUG
Priority:
Normal
Assignee:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version - Packaging:
Platform Release:
Target Release - Packaging:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
The script attempts to set NEEDSINFO on the upstream developer when a downstream bugzilla is set to Failed_QA. If that developer comments on the Bugzilla, the NEEDSINFO flag will be removed, however the script will reflag that developer with NEEDSINFO the next time it runs.
This is mostly an annoyance, because it leads to extra emails and extra edits to the Bugzilla by pulp-infra.
Updated by dalley over 6 years ago
- Subject changed from redmine_bugzilla script restores NEEDSINFO flag after it has been removed to redmine_bugzilla script restores NEEDSINFO flag on developer after it has been removed
- Description updated (diff)
Updated by ttereshc over 6 years ago
- Status changed from NEW to CLOSED - NOTABUG
- Triaged changed from No to Yes
It makes sense to keep an upstream developer (using needinfo flag) on FailedQA BZs until no more information from them is required. That indicates something is not resolved from the upstream side
Current workflow assumes that FailedQA flag will be unset together with needinfo flag if no more input from upstream is required.
Actions
.