[PATCH] Support list of users as options list in ticket custom field

[Zachary Bedell <zbedell@…>]

In the process of migrating from a Borland StarTeam install to Trac+SVN, I needed the ability to assign multiple users to a ticket. Borland provided the ability to include custom Change Request fields which could be limited to the list of valid users within the StarTeam project.

Attached is a patch which implements similar behavior in Trac. The patch introduces a simple variable replacement scheme to the options attribute of a custom ticket field. The INI section looks like this:

[ticket-custom]
devtest_assigned = select
devtest_assigned.label = Dev Tester Assigned
devtest_assigned.options = $userlist

Code in ticket/api.py checks for a select custom field which has an options attribute of literally "$userlist". If such a field is found, the field is passed to the existing function eventually_restrict_owner() to insert the listing of valid users.

The attached trivial three-line patch appears to work well against Trac-0.11.3.

[Zachary Bedell <zbedell@…>]

patch which implements this enhancement request

[Christian Boos]

See #2662.

[ismael@…]

The resolution is wrong, #2662 ticket is talking about something different.

This is not spam

[Remy Blank]

This ticket is indeed not a duplicate of #2662. Maybe the reference was wrong?

[jatyap <jatyap@…>]

attached patch does not work well with 0.12. Will a patch for 0.12 be released?

[Christian Boos]

Replying to rblank:

Maybe the reference was wrong?

No, this was an attempt of consolidating slightly different ways to approach the "multiple users assigned to a ticket" feature, which was also the starting point for this ticket according to the description.

See ticket:2662#comment:27 (this is one of the interests of the "timeline" links, as that comment was done right after comment:1 ;-) ).

Note that solution suggested in this ticket is also related to dynamic fields (#4374 and #4549).

[Andrew C Martin <andrew.c.martin@…>]

patch for trac 0.12-stable

[Andrew C Martin <andrew.c.martin@…>]

Replying to jatyap <jatyap@…>:

attached patch does not work well with 0.12. Will a patch for 0.12 be released?

I've posted attachment:ticket_custom_user_list-trac0.12.dev.patch​, which performs the same functionality as the original patch included with this ticket.

One issue to note: in both patches if a user logs in to trac for the first time ever, the custom fields which use the $userlist macro will not be updated until trac is restarted. I assume this is related to the @cached method decorator on def custom_fields.

Updated ticket summary with "[PATCH]" convention…

[derek@…]

@andrew nice one! for me it works like a charm

[larsivi@…]

@Andrew: Slightly off topic - did you use software to convert StarTeam CRs, milestones and such to Trac? If so, is it available somewhere? I'm aware of some softwares to do the changeset conversion to a different VCS, but not ticket conversion.

[Andrew C. Martin <andrew.c.martin@…>]

Replying to larsivi@…:

no, I did not.

[Ryan J Ollos]

Also requested in ​gmessage:trac-users:VTv3b5nAQNw/XLpNRGngCgAJ.

[Ryan J Ollos]

​TracUserSelectFieldPlugin has implemented a simple version of a user field. Comments on implementation in ​th:#13268.

[Ryan J Ollos]

See also comment:4:ticket:11469, which proposes a ICustomFieldTypeProvider interface.

[Ryan J Ollos]

Milestone renamed