Extract and abstract issue types.
At the moment, issue types seem a bit inflexible. Here are a few
thoughts:
* Move them into a plugin.
* Move their definition into config files and provide a set of examples
to get you started. Configuration could include type name, how it is
rendered in changelogs/ditz internal displays, etc. This also paves the
way for new issue types--support requests entered from a web interface,
for example.
* Make existing operators check for the plugin's presence, not
requiring it to be used.
Details
| Id: |
cf14c0aa1303a59355e04fb0f975f2b529791e13 |
| Type: |
feature |
| Creation time: |
2008-09-01 17:12 GMT |
| Creator: |
Nolan Darilek <nolan@...> |
| Release: |
unassigned
|
| Component: |
ditz |
| Status: |
unstarted
|
Commits for this issue
| 2008-09-01 17:13 GMT |
Nolan Darilek <nolan@...> |
Created issue. [72127be] |
|
Issue log
| 2008-09-03 03:38 GMT |
William Morgan <wmorgan-ditz@...> |
unassigned from release 0.6 |
|
| 2008-09-01 17:12 GMT |
Nolan Darilek <nolan@...> |
created |
|