[BUG-8000] Separate transaction notices from group notice/invites or provide some means for sorting incoming notifications. #15648
Comments
Adeon Writer commented at 2012-04-23T15:03:40Z I also experience all of the frustrations expressed here. Please address this issue. |
aki.shichiroji commented at 2012-04-23T15:26:33Z, updated at 2012-04-23T15:28:01Z Adding a suggested reworking of the notifications floater, including tabbed seperation of notification types (group, $ transactions, invites, system), the option to condense down to single title if needed (but by default set to show notice source, title of notice plus a few lines of the message. Each notice could still be 'X'ed off, but also each notice type could be cleared upon a cursory glance. ETA: ugh. sorry for the unnecessary watermark. i forgot to turn that off when exporting the photo out of Lightroom and can't delete the file from the JIRA. |
aki.shichiroji commented at 2012-04-23T15:29:41Z replacement graphic (removed extraneous watermarked attachment) |
aki.shichiroji commented at 2012-06-04T15:22:39Z Further notes on this issue: |
aki.shichiroji commented at 2012-08-12T18:39:58Z I recently had to deal with moving and duplicating around 120 product vendors, due to renovation. The current notification UI makes this a tedious and frustrating process. Because I use scripted vendors that handle a variety of sale options and incentives, this means I have to give debit permissions for each one. This task is slowed down at least by half in v3 due to the way system messages (such as debit permissions) are treated - anything that overflows the toasts (usually more than three) immediately get rerouted to the notifications listing, but because the messages there are always condensed, a second click is needed to open the message and click 'accept'. While in 1.23 I could easily power through hundreds within minutes, v3 not only requires you to open the message but to mouse away from the notifications chicklet to accept the message. This doesn't seem like a huge time waster, but consider that you'd be spending 2-3x the time going back and forth from notification list to actual message pop-up and multiply that by 100+ vendors and you can see how much of an inconvenience this becomes. There should be no reason why users should HAVE to rely on old viewers to power through what needs to be done, especially since the relative usefulness of 1.23 is dwindling in light of other improvements that did take place in the new UI. Yet every once in a blue moon, i have to pull 1.23 up simply because V3 falls down, badly, due to poor design and recognition of user needs. |
aki.shichiroji commented at 2014-12-10T03:17:47Z I can't seem to attach things to this JIRA any more since it's been moved to 'inactive', but i thought I'd link a version of the notifications floater I mocked up in Photoshop tonight, which more accurately reflects what I wish LL would impliment in the viewer: https://images.plurk.com/2nqO6brEZ0mw7vCSXYkGBR.jpg . I recently sent a suggestion using the new suggestions page, so perhapsthis deficiency will get some love from LL? One can only hope. |
Whirly Fizzle commented at 2014-12-10T11:38:58Z I attached it for you :) Aki, no-one really looks at these old VWR issues now. You may want to refile this issue in the BUG project as a new feature request. |
Alexa Linden commented at 2014-12-10T17:58:56Z Moved :) |
Alexa Linden commented at 2014-12-10T19:26:10Z This has been imported. |
Whirly Fizzle commented at 2015-01-09T20:20:44Z Oooh look what I see... :) |
aki.shichiroji commented at 2015-01-13T04:46:53Z This is great to hear! I hope we see the fruits of this work soon :) |
Grumpity Linden commented at 2015-02-27T00:14:31Z Whirly, you are soo sneaky! |
aki.shichiroji commented at 2015-05-05T10:32:24Z The bitbucket link appears to be dead - I don't see any projects for PavelK_productengine any more, nor are any of the commits as recent as mid-April apparent. Is this solution dead in the water? I haven't heard much on this for a while. I know there was mention of improvements to be made to the interface, but am dismayed to see progress on this topic apparently going dark. |
Whirly Fizzle commented at 2015-07-07T18:37:11Z Not dead in the water. See BUG-9625 and BUG-9626 ;) |
Grumpity Linden commented at 2015-07-08T18:32:59Z She's right as usual. It's not dead, it's out as a project viewer: https://community.secondlife.com/t5/Featured-News/New-Project-Viewer-Get-Your-Notifications-Sorted/ba-p/2947486 |
aki.shichiroji commented at 2015-07-12T01:11:06Z Glad to see it live! THanks for all your hard work :) |
Busy, established accounts often deal with high volumes of money transactions, group notices, group invites or inventory transfer. Notices for all of these things are collected in one small jumbled mess called the 'Notifications' chicklet. Users can open a corresponding Notifications floater, however this only provides one big long log for the user to scroll through. There is no way to easily pick out inventory transfer or group invites.
My notifications chicklet shows 99+ notifications several times a day and it is easy to miss important notices. While I could certainly turn off some of these notifications, this is not an ideal situation. As a merchant who is involved with her business, I prefer to keep track of incoming purchases. As an active group member, I often need to read info presented in group notices.
The current implementation does little to allow users to prioritize incoming information.
Please add some means of sorting these notifications out - both in their condensed (chicklet) and summary (floater) formats!
Thanks.
Attachments
Links
Related
Original Jira Fields
The text was updated successfully, but these errors were encountered: