Changes between Version 6 and Version 7 of BluePrintTicketing


Ignore:
Timestamp:
05/12/10 23:39:28 (12 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrintTicketing

    v6 v7  
    55A basic workflow app so that tasks can be logged for individuals or groups (pr_pentity without the dead bodies!).
    66
    7 Users can subscribe to their tasks via Email/SMS/Twitter/RSS - ideally based on category (such as priority/urgency).
    8  * Messaging module therefore needs to be moved up in the list of models.
     7Users can subscribe to their tasks via Email/SMS/Twitter/RSS - ideally based on category (such as location/project/priority/urgency).
     8 * [wiki:BluePrintMessagingModule Messaging module] therefore needs to be moved up in the list of models.
    99
    1010This can optionally be linked to a map:
    11  * http://wiki.sahana.lk/wiki/doku.php/req:ticketing
     11 * http://wiki.sahanafoundation.org/doku.php/req:ticketing
    1212
    13 What we have implemented so far is a Master Message Log where all inbound communications come (the !InBox for unclassified SMS, Emails, Tweets & Ushahidi Incidents).
     13What we have implemented so far is a Master Message Log where all inbound communications come (the !InBox for non-XForms SMS, Emails, Tweets & Ushahidi Incidents).
    1414
    1515These can be marked as Verified/Actionable/Actioned, Prioritised, Classified & Routed to other modules:
    16  * Alerting
     16 * Alerting (CAP, SMS, Email)
    1717 * Request Management System
    1818 * Situation Reporting (once available)
     
    2121----
    2222BluePrints
    23 BluePrints