Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #12173 (closed)

Opened 10 years ago

Closed 9 years ago

Bug: Smart way of submitting bugs from Insight

Reported by: atarkowska Owned by: jburel
Priority: major Milestone: 5.1.0-m4
Component: Insight Version: 5.0.1
Keywords: n.a. Cc: ux@…
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description

It turned out that when plate import failed feedback is send per image, that generate huge traffic in QA. Would be great to have that handled better and send one per plate.

Change History (10)

comment:1 Changed 10 years ago by jburel

  • Milestone changed from Unscheduled to 5.0.2
  • Owner changed from jburel to jburel, jamoore

A fix should also implemented on the QA front.
It might be a good time to re-activate the QA2 work. Insight File submission was modified for QA2.

comment:2 Changed 10 years ago by jamoore

  • Cc jamoore added
  • Owner changed from jburel, jamoore to jburel

comment:3 Changed 9 years ago by jburel

To be tested with QA2
Ola do you have a good example of plate that will fail to import?

comment:4 Changed 9 years ago by jburel

  • Cc ux@… added; jamoore removed

Petr; did you test that case while reviewing QA2?

comment:5 Changed 9 years ago by pwalczysko

Will proceed with simple try on a plate where I will damage one of the containing tiffs. If not successful, I will ask Ola.

comment:6 Changed 9 years ago by pwalczysko

Okay, so I think we have this atm (tested with damaged bd-pathway plate)

  • Insight tries to submit the whole plate at one go as one .zip.
  • it is successful in creating just one .zip but
  • the zip does not contain the whole plate
  • bd-pathway has 3 wells, .zip contains the last well only, whether you damaged the first or the second well, the result is the same
  • this means that the damaged .tiff is not contained in the submitted .zip
  • the bd-pathway folder has subfolders for each well, the unpacked .zip has only a flat structure
  • the .tiff files in the flat structure of the submitted .zip correspond always to the last well
Last edited 9 years ago by pwalczysko (previous) (diff)

comment:7 Changed 9 years ago by pwalczysko

@jburel: The damaged bd-pathway plates are on

team/jburel/broken plates from Petr/bd-pathway...

The number at the end of the plate name indicates which well contains the broken .tiff.
The .tiff was broken by opening it in text editor and deleting parts of it.

comment:8 Changed 9 years ago by jburel

Discussed today with Melissa,Chris and Emil:
It is preferable to block the submission of plate via QA, better to indicate to user to contact the team directly

comment:10 Changed 9 years ago by jburel

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.210242 sec.)

We're Hiring!