Skip to content
This repository has been archived by the owner on Aug 29, 2023. It is now read-only.

New / Edit Operation Step window: Time range fields are being reset #335

Closed
HelenClifton opened this issue Aug 29, 2017 · 2 comments
Closed
Assignees
Labels
Milestone

Comments

@HelenClifton
Copy link

Expected behavior

Using GUI to run through Use Case 6 happy path. Applied a subset_temporal operation.
In the “New Operation Step” window, selected a start time of 2007-01-01
Then cleared the end time field. Expected the start time which had just been entered not to change.

Actual behavior

The start time reset itself to 1980-01-01.

Notes:

  • Similar behaviour is seen if the end time has been entered and then the start time is cleared. The end time will reset itself to the current date.
  • Similar behaviour is seen in “Edit Operation Step” window as well as “New Operation Step” window
  • Similar behaviour is seen for other operations which contain a time range: anomaly_internal and open_dataset

Steps to reproduce the problem

  1. Ensure there is at least one resource of type Dataset in the workspace
  2. From operations panel, select subset_temporal then Apply
  3. In New Operation Step window, select a Dataset resource
  4. Next to TimeRange, enter a start time (the end time field is then automatically populated with today’s date)

capture1

  1. Clear the end time field and see that the start time has been reset to 1980-01-01

capture2

  1. Enter new end time

capture3

  1. Clear start time. Now end time has been reset.

capture4

Specifications

Cate 0.9.0-dev.5
Windows 7 Professional

@forman
Copy link
Member

forman commented Aug 31, 2017

We should switch to simple text fields.

@HelenClifton
Copy link
Author

Confirmed fixed in cate-0.9.0.dev.6

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants