Task #13067 (closed)
Opened 9 years ago
Closed 9 years ago
BUG: Cannot remove file attachment
| Reported by: | pwalczysko | Owned by: | dlindner |
|---|---|---|---|
| Priority: | blocker | Milestone: | OMERO-5.2.0 |
| Component: | Insight | Version: | OMERO-5.1.3 |
| Keywords: | n.a. | Cc: | ux@…, imunro-x |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by pwalczysko)
Cannot remove attachments in Insight.
Have a plate belonging to yourself.
Attach a file (from your local desktop, a text file) to it using insight or web.
Go to Insight and try to remove the file attachment - there is no remove menu on the single file attachments and the "minus" button on all the attachments does not work.
Present on 5.2 line on eel merge from today as well as in 5.1.3 client and 5.1.4 client connected to demo server.
Originally noticed by imunro-x and first troubleshot by khgillen
Note that on normal images, datasets and projects the behaviour is as expected (on 5.2 and 5.1 lines)
On 5.2 line, the inability to Remove is valid only for single attachments, the "big minus" on all attachments still works.
On 5.1 line, the possibility to remove any attachments from S/P/runs is zero though.
Change History (6)
comment:1 Changed 9 years ago by pwalczysko
- Description modified (diff)
comment:2 follow-up: ↓ 5 Changed 9 years ago by pwalczysko
comment:3 Changed 9 years ago by pwalczysko
- Milestone changed from OMERO-5.2.1 to OMERO-5.2.0
comment:4 Changed 9 years ago by dlindner
- Owner changed from jburel to dlindner
I'll take that over, working on the metadata panel anyway.
comment:5 in reply to: ↑ 2 Changed 9 years ago by khgillen
Replying to pwalczysko:
khgillen noted that the 5.1.3 insight client has this bug as well, this means it has been in for a while without any QA reports.
Also in 5.1.2 insight.
comment:6 Changed 9 years ago by dlindner
- Resolution set to fixed
- Status changed from new to closed
Possible candidate for 5.1.5 ? On the other hand, khgillen noted that the 5.1.3 insight client has this bug as well, this means it has been in for a while without any QA reports. Definitely needs fixing in 5.2 line.