History | Log In     View a printable version of the current page. Get help!  
   HOME       BROWSE PROJECT       FIND ISSUES       CREATE NEW ISSUE   
    QUICK SEARCH:  
Issue Details [XML]

Key: CHD-1495
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Assignee: Unassigned
Reporter: Joe Geck
Votes: 1
Watchers: 0
Operations

Clone this issue
If you were logged in you would be able to see more operations.
Cerberus Helpdesk

[Home Notifications] Entries cannot be marked read after customizing the view and logging out

Created: 12/Nov/09 02:04 PM   Updated: 18/Nov/09 10:34 AM
Fix Version/s: 4.3.1

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown


 Description   
Summary:
The notifications basically "lock up" and can't be removed from the view. As far as I know there is no user-friendly method (not hacking the db) to fix the problem.

1) Create a new home notification, sticky notes (notify myself) will work.
2) Customize the view, add a new column, etc.
3) Log out.
4) Log back in.
5) Try to mark the notification read. Either by clicking into it or using the dedicated button.

Result:
Entry is not removed from view.

Note:
I think it might be marked read behind the scenes in the database, as the "checkmark" icon disappears in the 'Read' column.

 All   Comments   Work Log   Change History      Sort Order:
Comment by Robert Middleswarth [12/Nov/09 02:06 PM]
[ Permlink ]
I have also seen this as well.

Thanks
Robert

Comment by Robert Middleswarth [12/Nov/09 02:13 PM]
[ Permlink ]
Some notes from me. The database shows them as being marked read (1). Also the Red Notification doesn't show unless there are unread (0) notifications and the number matches the number of unread. It looks like the filter read=0 is getting dropped off the view when being saved.

Thanks
Robert

Comment by Jeff Standen [WGM] [17/Nov/09 07:04 PM]
[ Permlink ]
Yeah, something funky is definitely happening here. I'm taking a look at it.

Comment by Jeff Standen [WGM] [17/Nov/09 07:16 PM]
[ Permlink ]
Fixed in 4.3.1 (948+)

Comment by Robert Middleswarth [17/Nov/09 08:48 PM]
[ Permlink ]
Confirm in my system that was having the issue and the problem went away once I pulled down the update. This looks good.

Thanks
Robert

Comment by Joe Geck [18/Nov/09 10:34 AM]
[ Permlink ]
Verified fixed in 4.3.1 dev build 949 (Git).

I checked on an "unbroken" installation and the problem is now fixed. Since Robert claims it was fixed retroactively when he updated against a broken build, I think we got the best of both worlds.

Closing out.



Powered by Atlassian JIRA™ (Standard Edition, Version: 3.3.1-#97) - Bug/feature request
Contact Administrators