#13067 closed defect (worksforme)
Cannot set new ticket owner using query string
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ticket system | Version: | 1.2.3 |
Severity: | normal | Keywords: | owner, new ticket, assign to |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
I have updated my trac from version 1.0.13 to version 1.2.3 on my Server. After the update I don't have the owner field anymore when creating a new ticket.
In the previous version it was also possible to have an URL with preset values (TracTickets#PresetValuesforNewTickets). This is working for all available input fields but not for the owner…probably because there is no owner input field. If I create a new ticket it is always owned by somebody…
The only way to set the owner is to click the Action "assign to" and select the owner, which is not what I am looking for.
Attachments (0)
Change History (3)
comment:1 by , 6 years ago
Description: | modified (diff) |
---|---|
Milestone: | → next-stable-1.2.x |
Summary: | owner does not appear in Version 1.2.3 → Cannot set new ticket owner using query string |
comment:3 by , 6 years ago
Milestone: | next-stable-1.2.x |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
In addition to the workflow, the ticket owner can also be controlled via [ticket]
default_owner
(TracTickets#DefaultValuesforDrop-DownFields, see also #11856). I can suggest the best solution if you provide more details about how you are using the new ticket query string. Are you using it to set the owner for all tickets, or is this a create ticket link in wiki text with field values that don't apply to all new tickets?
Edited TracTickets@82.
With Trac 1.2 you'll need to use the following query string (assuming you have the default workflow: ):
Replace "user1" with your preferred ticket owner.
Or, you can edit the default workflow (TracWorkflow#TicketCreateAction):
and use:
Note that changing the value of
default
will also reorder the create and assign to operations in the Action fieldset.I will give some thought as to whether we can restore the simplicity or
owner=...
in the query string. This is a side-effect of #2045 (see TracUpgrade#NewWorkflowActions) that I hadn't considered. However, the new ticket create actions are much more flexible so some additional complexity is to be expected.