hd:wishlist
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:wishlist [2005/10/15 21:29] – (old revision restored) 127.0.0.1 | hd:wishlist [2005/11/06 21:30] – fgm | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Ideas for 1.0 or minor releases after 1.0 ====== | ||
| - | * use theme functions to format blocks à la Drupal instead of hand-rolled HTML | ||
| - | * there should be a (per-user) setting for the maximum length of HD blocks before paging occurs: lists are currently unlimited | ||
| - | * there should be a site-wide setting for these values, acting as a default prior to user settings | ||
| - | * display a user's HD-related properties in hook_user(' | ||
| - | * for [[USER]]s: [[TICKET]]s, | ||
| - | * for [[CUSTOMER]]s: | ||
| - | * for [[TECH]]s: various stats, notably SLA-related. | ||
| - | |||
| - | ====== Ideas for next major release after 1.0 ====== | ||
| - | |||
| - | ===== Settings ===== | ||
| - | |||
| - | * a HD [[user]] can define whether (s)he wants one of the blocks made available by the module on his pages. A per-user setting could be added to define whether users wanting the blocks want them whether they are empty or not. | ||
| - | * a HD [[tech]] could be allowed to define the default behaviour for what happens : | ||
| - | * when customers are deleted: | ||
| - | * are their users and contracts moved to another customer uid (which one ?) or deleted, or kep orphans ? | ||
| - | * are the issues of their users affected ? | ||
| - | * when contracts are deleted | ||
| - | * are the events bound to them affected, and how ? | ||
| - | * when issues are deleted | ||
| - | * are followups deleted too, or bound to another issue, or kept orphans ? | ||
hd/wishlist.txt · Last modified: 2020/11/23 17:23 by 127.0.0.1