#330: Blocker Components are not updated when bug is reassigned
--------------------------------------+---------------------
Reporter: tflink | Owner: tflink
Type: defect | Status: new
Priority: major | Milestone:
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+---------------------
= bug description =
When a bug being followed by the blocker tracking app is reassigned to
another component, the component displayed in the tracker is never
updated.
This is a pretty big problem because it causes the current blockers to be
mis-represented if anything is re-assigned after it is proposed as a
blocker.
= bug analysis =
I looked into this a little during F18 and it doesn't appear to be quite
as simple as I was hoping. In theory, a full sync should take care of the
out-of-date data but that didn't fix the problem and I didn't see anything
obviously wrong with the sync code.
It is possible that #325 is interfering with the sync process - even
though the hacky fix made it into production, the sync was still crashing
on a regular basis.
= fix recommendation =
There are two parts to this bug.
* updated information is not being stored in the database
* change in component is not triggering an update
Changing the bugzilla query to pull in bugs when the component is updated
should be pretty easy - it's the part about new information not making it
into the database which is a bigger issue.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/330>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
