User Tools

Site Tools


hd:requirements

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
hd:requirements [2005/10/04 21:02] – (old revision restored) 127.0.0.1hd:requirements [2020/11/23 17:23] (current) – external edit 127.0.0.1
Line 2: Line 2:
  
 The helpdesk module will be noted "HD" for ease of writing. The helpdesk module will be noted "HD" for ease of writing.
 +
 +
 +
  
 ===== Nagging questions ===== ===== Nagging questions =====
Line 8: Line 11:
     * On the one hand, in many regards, they are to [[TICKET]]s what comments are to usual nodes on drupal     * On the one hand, in many regards, they are to [[TICKET]]s what comments are to usual nodes on drupal
     * On the other hand, there seems to be a trend amongst drupal developers (except the first of them :-() to move away from the current separate implementation of nodes and comments and towards a unified node implementation.     * On the other hand, there seems to be a trend amongst drupal developers (except the first of them :-() to move away from the current separate implementation of nodes and comments and towards a unified node implementation.
 +
 +  * User deletion in drupal involved removing the user's nodes, in our case [[TICKET]]s, [[FOLLOWUP]]s and, for [[CUSTOMER]]s, [[CONTRACT]]s. Is this acceptable behaviour ?
  
   * How will this assist with customer billing and record keeping?   * How will this assist with customer billing and record keeping?
Line 14: Line 19:
     * How can invoices be generated?     * How can invoices be generated?
  
- +Here is how I see it: 
- +  * credits and payments are created as tickets and followups with negative billed values, meaning their duration, when substracted from the running credit total, actually adds to it, extending the contract.  
- +  * tickets have a txnid linking back to a transaction in the ecommerce module, where all the financial part of billing is done. Of course, if using another ecommerce module, the txnid can be used to store a transaction id in this other module 
- +  * invoices are generated by the ecommerce module 
- +  * hours spent (or number of issues) are simply calculated per-contract by adding the duration entered for every followup bound to the contract
- +
- +
- +
- +
  
  
hd/requirements.1128459760.txt.gz · Last modified: 2020/11/23 17:23 (external edit)