Different argument list for newticket

[dean@…]

Starting in revision r4387, to get pre-filled fields you need to pass your arguments with a prefix of field_ so for example to send a type of defect you need to do /trac/newticket?field_type=defect instead of just ?type=defect. Sounds like an API change that might need to be fixed.

[Christian Boos]

Well, if we change it back, then we have to rename other parameters as well.

There's in particular version, that could be either the version field or the version of the ticket (we use a version parameter for identifying version of wiki pages as well).

Then, for custom field, you'd get the risk of a clash. Think about a custom field named format or action. Having them identified as field_… at least makes them unambiguous.

[Eli Carter]

I'd rather see all the internal variables renamed to _something than change the end-user interface for pre-filling fields.

[Christian Boos]

The dilemma comes mainly from version, which can also be seen as an end-user parameter, used also in the Wiki web_ui for example.

One possibility would be to rename version to revision for consistency with the versioncontrol web_ui (and keep backward compatibility with version in the wiki/web_ui).

We need at least to prefix the custom fields then. I'm not sure how future proof that will be, as with the GenericTrac approach, the distinction between custom and normal fields will probably go away. Using field_ would be more robust in this respect (or prop_ or another prefix, see also #5025).

[Christian Boos]

See #5025 and in particular comment 4.