Closed
Bug 415849
Opened 16 years ago
Closed 16 years ago
Notification settings changes don't stick
Categories
(Other Applications Graveyard :: QA Companion, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jay, Unassigned)
Details
Attachments
(1 file)
1.66 KB,
patch
|
Details | Diff | Splinter Review |
Not sure if it's just my profile(s), I tested with an old profile and a fresh one with a clean install of the extension, but if I make changes to the Notification settings, they don't persist after closing QAX. Things return to the original settings. We should fix this before release... IF notifications even work. I am not sure they do. If they aren't completely implemented, we can remove the check boxes for the v1. Zach/Clint: Any idea how far along we are with the notification code?
Updated•16 years ago
|
Product: Webtools → Other Applications
Version: Trunk → unspecified
Jay and I decided that due to time constraints we're just going to hide these settings and come back to them later. I'm checking in the patch above, Jay reviewed it over-my-shoulder. But the bug obviously still stands so I'm not marking it as fixed.
Assignee: zach → ctalbert
Status: NEW → ASSIGNED
Reporter | ||
Comment 3•16 years ago
|
||
No longer a blocker, but we should figure out what this feature should be doing and get it implemented for a future release.
Severity: blocker → major
I think the notification support is pretty cool, so making P2.
Priority: -- → P2
Comment 5•16 years ago
|
||
this was fixed by the patch for bug 397583
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Other Applications → Other Applications Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•