[Rt-devel] REST: should retrieving a particular attachment require a ticket number?

[Philip Kime]

Yes, that's what I realised after some code reading. I'll make the REST
API understand the "-a" flag and submit a patch.

PK 

-----Original Message-----
From: Jesse Vincent [mailto:jesse at bestpractical.com] 
Sent: 04 September 2006 19:23
To: Philip Kime
Cc: Jesse Vincent; rt-devel at lists.bestpractical.com
Subject: Re: [Rt-devel] REST: should retrieving a particular attachment
require a ticket number?




On Mon, Sep 04, 2006 at 07:19:50PM -0700, Philip Kime wrote:
> Actually, on further investigation, it seems that there is no public 
> API call to add attachments to a ticket - it's done inside a ->comment

> or
> ->correspond. You can add attachments on ticket create but this isn't
> allowed in the REST API. I may look at addressing this so the "-a" 
> flag can be used on ticket creation?

Attachments are on transactions. (Create, Comment or Reply) making it
work on create from the cli sounds sane.


> PK
> 
> -----Original Message-----
> From: Jesse Vincent [mailto:jesse at bestpractical.com]
> Sent: 04 September 2006 17:08
> To: Philip Kime
> Cc: Jesse Vincent; rt-devel at lists.bestpractical.com
> Subject: Re: [Rt-devel] REST: should retrieving a particular 
> attachment require a ticket number?
> 
> 
> 
> > as I'm not
> > > comfortable adding history-modifiying tools like that to RT.
> > 
> > Me neither. It's just I wanted to be able to attach things to 
> > tickets without having to do it via the "comment" command as this
sends mail.
> > Altering attachments is too dangerous, I agree. Changing the 
> > attachment or adding them should be logged in the history as usual.
> > Maybe an "attach" command for tickets is the way to go - like 
> > comment but without actually commenting?
> 
> Does it not actually create a correspond or comment transaction?
> 
> 
> --
> 

--