Task #12721 (new)
Opened 9 years ago
Last modified 8 years ago
RFE: Improve graphs error reporting in Web
| Reported by: | mtbcarroll | Owned by: | wmoore |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | Web | Version: | n.a. |
| Keywords: | n.a. | Cc: | ux@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
If an omero.cmd.GraphException is returned from a failed graph operation, its message can be used to provide a more user-readable error: see https://github.com/mtbc/openmicroscopy/commit/24039f25.
A move failure can be caused by projecting an image and trying to move only its projection; a delete failure can be caused by deleting a tag with which another user tagged their own image. (Or, myriad other ways!)
Change History (4)
comment:1 Changed 9 years ago by jamoore
- Owner changed from web-team@… to wmoore
comment:2 Changed 9 years ago by jamoore
- Milestone changed from 5.1.4 to OMERO-5.1.4
comment:3 Changed 9 years ago by sbesson
- Milestone changed from OMERO-5.1.4 to 5.x
As discussed with Will earlier today, pushing the non-critical Web tickets out of 5.1.4
comment:4 Changed 8 years ago by jamoore
- Milestone changed from 5.x to Unscheduled
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Splitting 5.1.4 due to milestone decoupling