hd:requirements
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| hd:requirements [2005/10/04 21:02] – (old revision restored) 127.0.0.1 | hd:requirements [2005/10/05 21:08] – (old revision restored) 127.0.0.1 | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| The helpdesk module will be noted " | The helpdesk module will be noted " | ||
| + | |||
| + | |||
| ===== Nagging questions ===== | ===== Nagging questions ===== | ||
| Line 14: | Line 16: | ||
| * How can invoices be generated? | * How can invoices be generated? | ||
| + | * User deletion in drupal involved removing the user's nodes, in our case [[TICKET]]s, | ||
| - | + | 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.txt · Last modified: 2020/11/23 17:23 by 127.0.0.1