Ticket #10453 (closed: fixed)
Better handle resetting variables for run
Reported by: | MarcusNoble | Owned by: | MarcusNoble |
---|---|---|---|
Priority: | critical | Milestone: | Release 3.3 |
Component: | Framework | Keywords: | AUTOREDUCTION |
Cc: | doucetm@…, tom.griffin@…, nick.draper@…, anders.markvardsen@… | Blocked By: | |
Blocking: | #10147, #10412 | Tester: | Anders Markvardsen |
Description (last modified by MarcusNoble) (diff)
When re-submitting a reduction run is isn't entirely clear what variables are being used.
Possible replace the "Reset to default variables" button with some sort of "Not the variables you were expecting?" link that shows a modal with more options.
Options:
- Variables used by selected run
- Default variables for original run number
- Default variables now
This change will also affect "run_summary" and and "run_confirmation" in the reduction_variables/views.py file
For Tester:
- Navigate to: http://datareducedev.isis.cclrc.ac.uk/autoreduce_webapp/runs/52172/0/
- Verify the action links on the right, hover over them and verify additional information is shown.
Change History
comment:3 Changed 6 years ago by MarcusNoble
- Status changed from inprogress to verify
- Resolution set to fixed
- Description modified (diff)
comment:4 Changed 6 years ago by Anders Markvardsen
- Status changed from verify to verifying
- Tester set to Anders Markvardsen
comment:5 Changed 6 years ago by Anders Markvardsen
- Status changed from verifying to reopened
- Resolution fixed deleted
For run #52355
Changing Testing to test9999.
Subsequent clickes on Reset to default values to not reset this parameter
comment:6 Changed 6 years ago by MarcusNoble
- Status changed from reopened to verify
- Resolution set to fixed
Now fixed. Please try again.
Note: See
TracTickets for help on using
tickets.