Opened 16 years ago
Closed 16 years ago
#3126 closed enhancement (fixed)
web admin interface for TicketSubmitPolicyPlugin
Reported by: | Jeff Hammel | Owned by: | Jeff Hammel |
---|---|---|---|
Priority: | normal | Component: | TicketSubmitPolicyPlugin |
Severity: | normal | Keywords: | webadmin |
Cc: | Trac Release: | 0.11 |
Description
it should be fairly straight forward to make a table (or tables) as a form where by one can alter the behavior of the TicketSubmitPolicyPlugin TTW instead of editting the .ini file. The basic form of this would be something like
* [type] [is|is not] [defect]: [requires] [version]
where each [field]
is a drop-down menu
Attachments (0)
Change History (2)
comment:1 Changed 16 years ago by
comment:2 Changed 16 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
the initial implementation is done as of r3996 ; the UI can be seen at http://trac-hacks.org/attachment/wiki/TicketSubmitPolicyPlugin/ticketsubmitadminUI.png
Some notes on this implementation:
- this is done entirely as a form using a POST request. JS could be used to make the form more intelligent and alter the form without POSTing; I think that the "Apply" button should remain and be a POST request so that the policy is consistently flushed when the user clicks the button
- the UI looks pretty bad; i'm not a UI designer, so any patches to the template that make things prettier would be appreciated
- the values for conditions are text-boxes; instead they should be widgets according to both the field type and and comparitor operator; in other words,
[type] [is] <input type="text" />
should actually use a <select>
tag instead of a text line. If the comparitor was "is in" instead of "is", instead of <select>
checkboxes should be used, as they are for the policy actions ( see /query )
There are a number of other minor tweaks that are desirable, but these are the top three. These and other issues with the webadmin interface should be ticketed separately.
we like the plugin a lot, but cannot us it as there is a "no productive file access" policy here. so this would be really helpful - to us anyway.