Bug 151901 - Bugzilla doesn't display assigned bugs
Summary: Bugzilla doesn't display assigned bugs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 2.18
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Lawrence
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-03-23 11:58 UTC by Robert Scheck
Modified: 2007-04-18 17:21 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-06-13 06:02:59 UTC
Embargoed:


Attachments (Terms of Use)

Description Robert Scheck 2005-03-23 11:58:18 UTC
Description of problem:
Bugzilla doesn't display assigned bugs at "My Front Page". "Open Issues: In 
Progress" should currently list bug #151632, but it doesn't (this bug is at 
the moment "assigned".

Version-Release number of selected component (if applicable):
Bugzilla Version 2.18

How reproducible:
Everytime

Actual results:
Bugzilla doesn't display assigned bugs

Expected results:
Assigned bugs should be listed in "Open Issues: In Progress"

Comment 1 William M. Quarles 2005-04-10 22:25:18 UTC
I'm having the same issue.

Comment 2 David Lawrence 2005-04-11 05:11:20 UTC
Taking ownership and researching.

Comment 3 Thomas Payerle 2005-04-21 22:06:45 UTC
I am seeing a similar issue in the past 10 days or so.  I am the requestor
on bug 147039, current status assigned.  I am quite sure it appeared in my
the "Open Issues: In Progress" section of the My Bugs page on 11 April when
I last updated the information, as it has been since the issue was opened.
Yesterday (20 Apr) I looked at the My Bugs page and it was not listed, and it 
remains that way now.  Using bugzilla 2.18.  The bug is in the system and can
be accessed by ID or searched upon, just appears to be omitted from the my
bugs page.

If I use the old BZ link (bugzilla 2.17) the bug does currently appear in the
My Bugs as I expect.  

Comment 4 Robert Scheck 2005-06-12 12:34:44 UTC
Hey, seems to work now...maybe someone else gets the same fine result before 
closing this bug report?

Comment 5 William M. Quarles 2005-06-13 05:36:29 UTC
I am satisfied that this has been repaired.  Suggest changing bug status to
"RESOLVED."

Comment 6 Robert Scheck 2005-06-13 06:02:59 UTC
Closing with "CURRENTRELEASE", there's no "RESOLVED" or better :-(


Note You need to log in before you can comment on or make changes to this bug.