Ticket #8429 (closed: fixed)
[ICAT] Empty run range issues
Reported by: | Jay Rainey | Owned by: | Jay Rainey |
---|---|---|---|
Priority: | minor | Milestone: | Release 3.1 |
Component: | GUI | Keywords: | ICAT, ICAT4 |
Cc: | Blocked By: | ||
Blocking: | Tester: | Samuel Jackson |
Description
If the run-range for an investigation is empty and the start date is not, then the start date is inserted into the run-range cell and the related end-date is inserted into the start-date cell.
To see this problem, perform a search between 27/09/2013 and 28/11/2013.
Change History
comment:2 Changed 7 years ago by Jay Rainey
- Status changed from inprogress to verify
- Resolution set to fixed
Prior to testing I suggest running through the test below to see the problem. You will see that the start and end dates are in the wrong columns (they are in run-range, and start-date respectively).
To test
- Open Mantid and log into the catalog.
- Perform a search with start date as 11/09/2013 and end date as 28/11/2013.
- Notice that the data now appears in the correct and related column/cell.
comment:3 Changed 7 years ago by Samuel Jackson
- Status changed from verify to verifying
- Tester set to Samuel Jackson
comment:4 Changed 7 years ago by Samuel Jackson
- Status changed from verifying to closed
Merge remote-tracking branch 'origin/feature/8429_icat_run_range_issue'
Full changeset: 9179756045d7782c372b7270f32ed754c73a140e
Note: See
TracTickets for help on using
tickets.
Add empty string to cell if value does not exist. Refs #8429.
Changeset: f92633962a5c370ec7f373ef5d72ad5a50953a70