Changes between Initial Version and Version 1 of Ticket #7994


Ignore:
Timestamp:
Nov 5, 2010, 1:30:28 PM (13 years ago)
Author:
osimons
Comment:

Mailing list would be better for "support" issues...

Anyway, the basic idea is:

  1. Use ticket.getActions(int id) to get all available actions for the ticket. The documentation for this command says: "Returns the actions that can be performed on the ticket as a list of [action, label, hints, [input_fields]] elements, where input_fields is a list of [name, value, [options]] for any required action inputs.". It will return the actions allowed by the user on the ticket in current state, and with any additional fields - like the web form does.
  2. To attributes you add 'action', for instance 'reassign'. But, as from 1. above you would see that reassigning includes a separate input field, that field must also be added. So, the minimum attributes posted would need to be {'action': 'reassign', 'action_reassign_reassign_owner': 'osimons'}.

OK?

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #7994

    • Property Status changed from new to closed
    • Property Resolution changed from to worksforme
  • Ticket #7994 – Description

    initial v1  
    1414
    1515I am usinc xmlrpc via c# and have a standard workflow.
     16{{{
    1617accept = new,assigned,accepted,reopened -> accepted
    1718accept.operations = set_owner_to_self
     
    2930resolve.operations = set_resolution
    3031resolve.permissions = TICKET_MODIFY
     32}}}