-
Bug
-
Resolution: Handled by Support
-
Low
-
None
-
2.2.0
-
None
-
None
We've had some issues where someone broke Crowd (they changed the LDAP credentials it was using).
One nasty side effect of this is that fisheye stopped sending notifications out. The real nuisance though is that all watchers appeared to be removed and needed adding back in manually.
I've afraid I've not got the full logs anymore but I can tell you this much:
(watcher error)
2010-04-14 00:00:00,097 ERROR [FE-WatchChecker] fisheye.app com.cenqua.fisheye.web.WatchManager$WatchChecker-checkWatchesForRep - Could not create trusted user login for user [mikeh]. Notification skipped for this user.
[FE-2578] fisheye loses notifications upon crowd issues
Workflow | Original: FE-CRUC Bug Workflow [ 2944188 ] | New: JAC Bug Workflow v3 [ 2957201 ] |
Workflow | Original: FECRU Development Workflow - Triage - Restricted [ 1517901 ] | New: FE-CRUC Bug Workflow [ 2944188 ] |
Workflow | Original: FECRU Development Workflow - Triage [ 943080 ] | New: FECRU Development Workflow - Triage - Restricted [ 1517901 ] |
Workflow | Original: FECRU Development Workflow (Triage) [ 309748 ] | New: FECRU Development Workflow - Triage [ 943080 ] |
Workflow | Original: Simple review flow with triage [ 209771 ] | New: FECRU Development Workflow (Triage) [ 309748 ] |
Resolution | New: Handled by Support [ 8 ] | |
Status | Original: Needs Triage [ 10030 ] | New: Closed [ 6 ] |
Hi Adrian,
Sorry for the slow response, this is our development planning instance of JIRA - for timely response on urgent matters, can you please raise a ticket at http://support.atlassian.com.
This may be a bug, but we will close it until our support engineers can come up with a solid diagnosis.
Matt