Ticket #77 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

Event Priority Defaults

Reported by: ssmith Assigned to: ssmith
Priority: normal Milestone: Week 32
Component: General Version:
Severity: normal Keywords:
Cc:

Description

Priorities default to Priority 1.

We need to change the default to something lower, as we don't want all new events to go into the headline selector.

Change History

06/08/05 02:53:46 PM changed by obaltzer

The priority should be set to NULL since this is the only reasonable default value I can think of. Any other explicit value is site-specific. Additionally, the select field for priorities should include a None priority which corresponds to a priority of NULL.

08/08/05 10:56:21 AM changed by ssmith

  • owner changed from somebody to ssmith.

13/08/05 11:24:54 AM changed by ssmith

  • status changed from new to closed.
  • resolution set to fixed.

Our dummy data has a 'Normal' event listing with a value of 100. Since I am unsure of how to go about making sure there is a 'None' category with a value of nil when priorities are pulled from a database, I am setting new events to have the 'Normal' priority.

Technically, they are the same thing anyway.

Completed in changeset [122]