#7284 closed enhancement (duplicate)
updating tickets with xmlrpc in the name of a different user
Reported by: | seniorsamu | Owned by: | osimons |
---|---|---|---|
Priority: | normal | Component: | XmlRpcPlugin |
Severity: | normal | Keywords: | submitter |
Cc: | Trac Release: | 0.11 |
Description
When a ticket is created using xmlrpc, the user can specify the reporter field so that a single user can be used from the calling program to do all ticket creation. However, when a change has to be introduced, this solution does not work, as with the ticket update xmlrpc call you cannot specify the changer. Implementing a small change in the plugin provides this capability.
In order to achieve this, we introduce an additional attribute to calling ticket.update. This is 'changer'. If the attribute is present then the changer will be logged as to who performed the change, otherwise the user who is authenticated. The attached patch introduces this change.
As this change does not affect current functionality, rather it adds further functions, I would be glad to see this change integrated into xmlrpc. However, didn't have a chance to check if this change affects any of the other extenstions working with xmlrpc, but as all current functionality remains I see little problem there.
Attachments (1)
Change History (3)
Changed 15 years ago by
Attachment: | ticket.patch added |
---|
comment:1 Changed 14 years ago by
Resolution: | → duplicate |
---|---|
Status: | new → closed |
This really is a duplicate of #5445, isn't it? That also has a patch. I'm closing this one and referring back here from the older ticket.
comment:2 Changed 14 years ago by
You are right. In fact, this is a duplicate of that defect. Thanks for pointing out.
This patch has to be applied on ticket.py in the xmlrpc package