WebIssues 0.9.4-beta2 (Client branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News WebIssues 0.9.4-beta2 (Client branch)
# 1  
Old 01-11-2009
WebIssues 0.9.4-beta2 (Client branch)

Image WebIssues is a system that supports team collaboration across the Internet. It can be used for storing bugs and other information with customizable attributes, comments, and file attachments. The server can be installed on any host with PHP and MySQL, PostgreSQL, or MS SQL Server. The client is a native desktop application for both Windows and Linux. License: GNU General Public License (GPL) Changes:
This version extends support for email notifications by adding automatic notifications for modified issues in selected folders. It also adds command line options for overriding default file locations and fixes a few bugs. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
RT::Client::REST::Attachment(3pm)			User Contributed Perl Documentation			 RT::Client::REST::Attachment(3pm)

NAME
RT::Client::REST::Attachment -- this object represents an attachment. SYNOPSIS
my $attachments = $ticket->attachments; my $count = $attachments->count; print "There are $count attachments. "; my $iterator = $attachments->get_iterator; while (my $att = &$iterator) { print "Id: ", $att->id, "; Subject: ", $att->subject, " "; } DESCRIPTION
An attachment is a second-class citizen, as it does not exist (at least from the current REST protocol implementation) by itself. At the moment, it is always associated with a ticket (see parent_id attribute). Thus, you will rarely retrieve an attachment by itself; instead, you should use "attachments()" method of RT::Client::REST::Ticket object to get an iterator for all attachments for that ticket. ATTRIBUTES
id Numeric ID of the attachment. creator_id Numeric ID of the user who created the attachment. parent_id Numeric ID of the object the attachment is associated with. This is not a proper attribute of the attachment as specified by REST -- it is simply to store the ID of the RT::Client::REST::Ticket object this attachment belongs to. subject Subject of the attachment. content_type Content type. file_name File name (if any). transaction_id Numeric ID of the RT::Client::REST::Transaction object this attachment is associated with. message_id Message ID. created Time when the attachment was created content Actual content of the attachment. headers Headers (not parsed), if any. parent Parent (not sure what this is yet). content_encoding Content encoding, if any. METHODS
RT::Client::REST::Attachment is a read-only object, so you cannot "store()" it. Also, because it is a second-class citizen, you cannot "search()" or "count()" it -- use "attachments()" method provided by RT::Client::REST::Ticket. retrieve To retrieve an attachment, attributes id and parent_id must be set. INTERNAL METHODS
rt_type Returns 'attachment'. SEE ALSO
RT::Client::REST::Ticket, RT::Client::REST::SearchResult. AUTHOR
Dmitri Tikhonov <dtikhonov@yahoo.com> LICENSE
Perl license with the exception of RT::Client::REST, which is GPLed. perl v5.14.2 2011-12-27 RT::Client::REST::Attachment(3pm)