You are here: start » req » ticketing

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision 		Previous revision
req:ticketing [2009/09/02 00:07]
tim created 		req:ticketing [2010/12/18 17:35] (current)
Line 1: Line 1:
-====Background====+=====Background=====
  
 It should be easy to enter information about the situation, create a task from that event and then track the progress of that task. It should be easy to enter information about the situation, create a task from that event and then track the progress of that task.
Line 6: Line 6:
  
  
-==== Workflow ====+===== Workflow =====
  
-=== Info In ===+   Note, the screenshots below are an attempt at a new user interface. 
 +   Comments welcome. 
 + 
 +==== Info In ====
  
 Users have a text area field and map occupying half of the screen each. Users have a text area field and map occupying half of the screen each.
  
 A message/update received via MMS, phone, VHF, email, etc. This info is then entered into the textfield. Email/SMS messages have their text automatically inserted into the text area. A geographic point on the map is clicked, to provide location information. A message/update received via MMS, phone, VHF, email, etc. This info is then entered into the textfield. Email/SMS messages have their text automatically inserted into the text area. A geographic point on the map is clicked, to provide location information.
 +==== Task Creation + Allocation ====
  
-=== SitRep Generation ===+Each feature on the map should be able to turned into a task. These tasks should be able to be allocated to other users, groups or organisations.
  
-Users go through the log of events and select if it is "SitRep Siginifcant". This subset of messages is automatically ported to the situation reporting module for manipulation.+{{:req:map_new_object.png?400}}
  
 +=== Notes to diagramme ===
 +
 +  * "Allocate Task To" uses JQuery/AJAX autocomplete for speed.
 +  * Submit buttons to be created
 +
 +==== Event Detail ====
 +
 +{{:req:map_object.png?400}} 
 +
 +==== Task Followup ====
 +
 +Authorised users should be able to review the status of the requests.
 +
 +==== Event Log ====
 +
 +A detailed event log should be able to be easily generated.
 +
 +
 +
 +
 +===== Other components =====
 +==== Congruence with Situation Awareness module ===
 +
 +   I've provisionally renamed Situation Awareness to Situation. Feels better.
 +
 +The task edit and allocation functionality should tie in perfectly with the situation awareness module.
 +
 +=== Overview ===
 +
 +  * General view of the current active events.
 +  * Selecting a marker brings up a new, see below.
 +  * Experimenting with different types of markers, so that Sahana doesn't look so Google Maps-esque.
 +
 +{{:req:map_view.png?400}}
 +
 +=== Map, with item selected ===
 +
 +  *
 +  * Exclamation mark indicating severity.
 +
 +{{:req:map_view_select.png?400}} 
 +
 +==== SitRep Generation ====
 +
 +Users go through the log of events and select if it is "SitRep Siginifcant". This subset of messages is automatically ported to the situation reporting module for manipulation.
  
 +==== Sidebar ====
  
 +A sidebar that appears on all modules. It is populated by a list of tasks that are currently allocated to that user, possibly with a small map the is zoomed to a level that allows the location of all the events that generated the maps to be shown.

Trace:

QR Code
QR Code req:ticketing (generated for current page)