This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Since, in general, it's hoped that the original reporter of a bug will verify it after it's been fixed, it's inconvenient that the "My Issues" links don't show the issues which have been marked RESOLVED FIXED, but which are still waiting for you to verify the fix. IMHO, it would be more useful if they didn't disappear from this list until they were marked VERIFIED, and might encourage people to get round to verifying them a bit more often.
Excellent suggestion! Passing on to Collab.
Logged this internally as PCN11104. Thanks, Kristen
A target milestone has not yet been assigned to this issue. Our plan is to update the issue as soon as we have more information from Product Management. The support team does check on these issues regularly. Please let us know if there are any additional considerations for this enhancement request or concerns on the timeframe for the next update. Thanks, Jan
Change in our Update Plan: Our plan is to update this issue in 2 weeks. Please let us know if there are any additional thoughts on this issue or concerns about the timeframe for the next update. Jan
Update: In SourceCast 2.0 and later releases the My Issues query can be configured on a per project basis. If the general policy is to include RESOLVED FIXED issues in the query results then the My Issues query can be changed for all users. (Later, in the Project tracker, based on Scarab, the user can define their own My Issues query.) Action Plan: Looking into how the query can be changed for all users if Netbeans agrees that this should be implemented. Next Update: Within 2 weeks.
Update: Requested more information on implementation from Engineering. Action Plan: Awaiting response. Next Update: By 12-13-02 Thanks, Kristen
update: the management confirmed that what Kristen asked from management: 'this can be configured on a per-project basis even in single db mode.' Action plan: closing this issue and will confirm/verify it after the upgrade.
Sorry, i meant closing.
Verified that the issue has been fixed. Regards, Karishma Support Operations
We recently moved out from Collabnet's infrastructure