track blockers closed as duplicates to non-blockers #13

New issue

Open

opened 2014-01-13 14:02:13 +00:00 by mkrizek · 4 comments

mkrizek commented

2014-01-13 14:02:13 +00:00

Moved from trac https://fedorahosted.org/fedora-qa/ticket/318 :
"When bug A (proposed/accepted blocker) is closed as a duplicate of bug B (not proposed as a blocker), it disappears from the list. Unfortunately a lot of developers won't transfer the Blocks: and Whiteboard: fields, so we might lose track of some important bugs this way.

Displaying A or B in the list even when this happens would be nice. Displaying B is probably the preferable way. There could be a special icon indicating that B is displayed because of recursive dependencies and tooltip would specify it is because of bug A."

Moved from trac [[ https://fedorahosted.org/fedora-qa/ticket/318 | https://fedorahosted.org/fedora-qa/ticket/318 ]]: "When bug A (proposed/accepted blocker) is closed as a duplicate of bug B (not proposed as a blocker), it disappears from the list. Unfortunately a lot of developers won't transfer the Blocks: and Whiteboard: fields, so we might lose track of some important bugs this way. Displaying A or B in the list even when this happens would be nice. Displaying B is probably the preferable way. There could be a special icon indicating that B is displayed because of recursive dependencies and tooltip would specify it is because of bug A."

tflink commented

2014-01-14 18:48:47 +00:00

Contributor

While this is a problem, I don't see it as something that we're going to get to soon. Changing priority to "wishlist"

adamwill commented

2020-03-24 18:31:11 +00:00

Owner

I think Bugzilla has actually made this less of a problem lately by actually transferring Blocks: when you close a bug as a dupe...there may still be cases to cover here (I don't think it transfers Whiteboard values, so accepted status wouldn't be transferred, I don't think), but I don't think it's as bad as it was.