Ticket #93 (closed enhancement: fixed)

Opened 6 years ago

Last modified 5 years ago

separate out input of Events, Sampling Events and EventGroups

Reported by: kees.vanbochove@… Owned by: kees.vanbochove@…
Priority: minor Milestone: 0.8.1
Component: Study create/edit wizard Version:
Keywords: Cc:
Hardware: Operating system:
Product: URL:

Description

the current event input screen in the study is too complex. The new setup should be:

input just the number of EventGroups?, generate them, and then give a possibility to change the names

  • Events page:

input of Events, same as it is now, but with the defined groups

  • SamplingEvents? page:
  • input of SamplingEvents?, same as it is now, but with the defined groups
  • but by default, all events checked for all groups
  • and endDate should be by default same as startDate

Change History

comment:1 Changed 6 years ago by work@…

  • Status changed from new to assigned
  • Owner set to business@…
  • Component set to Export functionality

opened 6 months ago... setting milestone 0.6.2 and assigning to Kees... can this be closed?

comment:2 Changed 6 years ago by work@…

  • Milestone set to 0.6.2

comment:3 Changed 6 years ago by business@…

  • Owner changed from business@… to work@…
  • Milestone changed from 0.6.2 to 0.7

Think of a more clear way to distinguish sampling events from events

comment:4 Changed 6 years ago by work@…

this should be picked up after refactoring is done. Leaving this for now in 0.7 but most likely this should move to 0.8 instead

comment:5 Changed 5 years ago by work@…

  • Priority changed from major to minor
  • Component changed from Export functionality to Study create/edit wizard

comment:6 Changed 5 years ago by work@…

  • Milestone changed from 0.7 to 0.8

comment:7 Changed 5 years ago by work@…

  • Owner changed from work@… to kees.vanbochove@…
  • Milestone changed from Could have to 0.8.1

resolved in r1782

comment:8 Changed 5 years ago by work@…

  • Status changed from assigned to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.