ticket,summary,type,release,owner,status,created,modified,_description,_reporter
12161,CC-Selector button position incorrect since Trac 1.0.3,defect,1.0,,new,2015-01-26T03:21:37+01:00,2016-12-02T23:52:17+01:00,"In Trac 1.0.1 the CC-select button ("">"") was to the right of the CC field, but to the left of the vertical line separating left- and right-hand columns of fields.

Since 1.0.3 (we skipped 1.0.2 update) the CC field was made longer, so the CC button overwrites the field to the right of CC.

The CC Selector button should either be moved to a different position (where?) or else the CC-S code should shorten the CC: field back to the old length, so there is space.

See attached screenshot.",Jeremy Dunn
8491,No permission checking when requesting users,defect,0.12,,new,2011-02-10T15:19:09+01:00,2016-12-02T23:52:17+01:00,"Requests to `/cc_selector` will return emails of all users with ticket permissions, without checking any permission for the user actually requesting the data. At least `TICKET_EDIT_CC` permission should be required. This means:
 1. Checking permission before injecting the script in ticket pages
 2. Using `req.perm.require('TICKET_EDIT_CC')` in `process_request()`

BTW, having `re.search('ticket', req.path_info)` will catch a lot of unintended requests - including source code paths or wiki pages that may have 'ticket' in the name. Better would be to just check for `template == 'ticket.html'`.
",osimons
8719,Status of action radio button is set to wrong option after refreshing an existing ticket,defect,0.12,,new,2011-04-19T11:50:28+02:00,2016-12-02T23:52:17+01:00,"When I view an existing ticket and hit the refresh button in my browser, the action radio button is set to 'resolve as fixed' instead of the first 'leave as accepted' status, see the attached screenshot. I use the custom workflow as shown below, but the behavior is exactly the same in a completely new default Trac 0.12 environment.

{{{
[cc_selector]
show_fullname = false
username_blacklist = admin, development, extern

[ticket-workflow]
accept = new,assigned,accepted,reopened,input needed -> accepted
accept.operations = set_owner_to_self
accept.permissions = TICKET_MODIFY
leave = * -> *
leave.default = 1
leave.operations = leave_status
need input = new,assigned,accepted,reopened,input needed,closed -> input needed
need input.operations = set_owner
need input.permissions = TICKET_MODIFY
reassign = new,assigned,accepted,reopened,input needed -> assigned
reassign.operations = set_owner
reassign.permissions = TICKET_MODIFY
reopen = accepted,closed,input needed -> reopened
reopen.operations = del_resolution
reopen.permissions = TICKET_CREATE
resolve = new,assigned,accepted,reopened,input needed,closed -> closed
resolve.operations = set_resolution
resolve.permissions = TICKET_MODIFY
}}}",devscan
9643,Add default sorting to CC selector plugin,enhancement,0.12,,new,2011-12-29T18:44:12+01:00,2016-12-02T23:52:17+01:00,"If there are many developers the cc list can get quite long.  By simply adding the sorted() function in templates/cc_selector.html on line 31 the names will be alphabetized.


{{{
for=""d in sorted(cc_developers)""
}}}
",grimmdude