Re: [Fedora QA] #427: track page does not show bug set as final blocker

2013-10-16 Thread Fedora QA 
#427: track page does not show bug set as final blocker
---+-
  Reporter:  chrismurphy   |  Owner:  tflink
  Type:  enhancement   | Status:  closed
  Priority:  minor |  Milestone:  Undetermined Future
 Component:  Blocker bug tracker page  |Version:
Resolution:  fixed |   Keywords:
Blocked By:|   Blocking:
---+-

Comment (by adamwill):

 Yep, sorry for the finicky process :( Obviously if we weren't abusing BZ
 for this purpose we could make it more robust.

 One question that occurs is whether the blocker bug proposal app handles
 this properly when re-proposing a previously rejected bug - tflink?

-- 
Ticket URL: https://fedorahosted.org/fedora-qa/ticket/427#comment:3
Fedora QA http://fedorahosted.org/fedora-qa
Fedora Quality Assurance
___
qa-devel mailing list
qa-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/qa-devel

Re: [Fedora QA] #427: track page does not show bug set as final blocker

2013-10-16 Thread Fedora QA 
#427: track page does not show bug set as final blocker
---+-
  Reporter:  chrismurphy   |  Owner:  tflink
  Type:  enhancement   | Status:  closed
  Priority:  minor |  Milestone:  Undetermined Future
 Component:  Blocker bug tracker page  |Version:
Resolution:  fixed |   Keywords:
Blocked By:|   Blocking:
---+-

Comment (by tflink):

 Replying to [comment:3 adamwill]:
  Yep, sorry for the finicky process :( Obviously if we weren't abusing BZ
 for this purpose we could make it more robust.
 
  One question that occurs is whether the blocker bug proposal app handles
 this properly when re-proposing a previously rejected bug - tflink?

 We've had this conversation before and I still don't have a strong opinion
 on it. We can change the app to ignore !RejectedBlocker in the whiteboard
 but in my mind, that brings up a question of whether we want to just drop
 that part of the process entirely.

-- 
Ticket URL: https://fedorahosted.org/fedora-qa/ticket/427#comment:4
Fedora QA http://fedorahosted.org/fedora-qa
Fedora Quality Assurance
___
qa-devel mailing list
qa-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/qa-devel

[Fedora QA] #427: track page does not show bug set as final blocker

2013-10-15 Thread Fedora QA 
#427: track page does not show bug set as final blocker
--+--
 Reporter:  chrismurphy   |   Owner:  tflink
 Type:  enhancement   |  Status:  new
 Priority:  minor |   Milestone:  Undetermined Future
Component:  Blocker bug tracker page  | Version:
 Keywords:|  Blocked By:
 Blocking:|
--+--
 = bug description =
 A bug with Blocks field set to 689509, 980651, 980656 does not show up on
 the tracker's final blocker page; probably because it was rejected as a
 beta blocker therefore it has Whiteboard set to RejectedBlocker.

 = bug analysis =
 https://bugzilla.redhat.com/show_bug.cgi?id=864198

 = fix recommendation =

 Ideally a way for rejected blockers to be differentiated from separately
 proposed blockers; e.g. Whiteboard RejectedBetaBlocker vs
 RejectedFinalBlocker.

 Otherwise, if approved for final blocker, it seems like it will just
 suddenly appear in the final blocker listing rather than having been on
 notice as a proposed final blocker.

-- 
Ticket URL: https://fedorahosted.org/fedora-qa/ticket/427
Fedora QA http://fedorahosted.org/fedora-qa
Fedora Quality Assurance
___
qa-devel mailing list
qa-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/qa-devel

Re: [Fedora QA] #427: track page does not show bug set as final blocker

2013-10-15 Thread Fedora QA 
#427: track page does not show bug set as final blocker
---+-
  Reporter:  chrismurphy   |  Owner:  tflink
  Type:  enhancement   | Status:  closed
  Priority:  minor |  Milestone:  Undetermined Future
 Component:  Blocker bug tracker page  |Version:
Resolution:  fixed |   Keywords:
Blocked By:|   Blocking:
---+-
Changes (by tflink):

 * status:  new = closed
 * resolution:   = fixed


Comment:

 Yeah, since we have no way of determining which tracker the
 !RejectedBlocker refers to, the app assumes that it's rejected for all
 of them.

 I removed the !RejectedBlocker and blocks on the beta tracking bug so
 that it'll be detected as a proposed final blocker.

-- 
Ticket URL: https://fedorahosted.org/fedora-qa/ticket/427#comment:1
Fedora QA http://fedorahosted.org/fedora-qa
Fedora Quality Assurance
___
qa-devel mailing list
qa-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/qa-devel

Re: [Fedora QA] #427: track page does not show bug set as final blocker

2013-10-15 Thread Fedora QA 
#427: track page does not show bug set as final blocker
---+-
  Reporter:  chrismurphy   |  Owner:  tflink
  Type:  enhancement   | Status:  closed
  Priority:  minor |  Milestone:  Undetermined Future
 Component:  Blocker bug tracker page  |Version:
Resolution:  fixed |   Keywords:
Blocked By:|   Blocking:
---+-

Comment (by chrismurphy):

 Ok so this was user error. I'm supposed to remove both Whiteboard:
 RejectedBlocker and the Blocker: blockbug# when reproposing for a
 different blocking bug. Sorry about that.

-- 
Ticket URL: https://fedorahosted.org/fedora-qa/ticket/427#comment:2
Fedora QA http://fedorahosted.org/fedora-qa
Fedora Quality Assurance
___
qa-devel mailing list
qa-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/qa-devel