Skip to content

Manage Issues

Issues

Issues are managed from the Issues Page. These are automated notices generated by the backend system in OLIVE whenever an event or problem occurs related to data processing.

The page contains a basic data grid with cross-filtering options. See the sections on working with data grids and filtering with charts for more information.

There are four status types:

  • Active - all issues requiring attention start out in this state, and are also given a (albeit subjective) priority of Low, Medium, or High.
  • Resolved - An issue may be edited and set to Resolved if the issue was diagnosed and action was taken.
  • Closed - An issue may be edited and set to Closed if no problems were found and/r no action was taken (e.g., a false alarm).
  • Info Only - System events that do not require attention and are simply recording that an action occurred are given the "Info Only" status and are hidden by default when the page loads; the page filter is used to daylight these events.

Issue Details

  • Issue Name - this briefly identifies the nature of the issue
  • Description - error output and/or narrative description of the issue. This may include GUID keys for database records or other diagnostic information that is useful for developers.
  • Project Name - if a project can be identified for the issue, this is noted here
  • Priority - subjective scale of severity of the issue
  • Status - discussed above
  • Type - issue category
  • Entity type - data type category (field visit, timeseries data, etc)
  • Assigned User - This is blank by default. It can be used to assign a problem to a specific person (.e.g, by a manager) or is used to identify who revolved/closed the issue.

Typical Issue Lifecycle

  1. A new issue is created by the system. It appears on the Compliance Dashboard is noted by a system user.
  2. The appropriate person is assigned to address the issue.
  3. After investigation, the assignee edits the issue, adding a note to the end of the Description describing what actions were taken.
  4. Issue is set to Resolved/Closed (see above for the distinction).

In certain circumstances, an issue may simply be deleted instead of closed out. These would include system tests, such as sending a dummy file through the manual upload process, or multiple records associated with the same underlying issue.