Return-Path: X-Original-To: apmail-bloodhound-user-archive@www.apache.org Delivered-To: apmail-bloodhound-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2741718000 for ; Sun, 8 Feb 2015 13:18:04 +0000 (UTC) Received: (qmail 48554 invoked by uid 500); 8 Feb 2015 13:18:04 -0000 Delivered-To: apmail-bloodhound-user-archive@bloodhound.apache.org Received: (qmail 48523 invoked by uid 500); 8 Feb 2015 13:18:04 -0000 Mailing-List: contact user-help@bloodhound.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@bloodhound.apache.org Delivered-To: mailing list user@bloodhound.apache.org Received: (qmail 48512 invoked by uid 99); 8 Feb 2015 13:18:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Feb 2015 13:18:04 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of olemis@gmail.com designates 209.85.223.180 as permitted sender) Received: from [209.85.223.180] (HELO mail-ie0-f180.google.com) (209.85.223.180) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Feb 2015 13:17:59 +0000 Received: by iecat20 with SMTP id at20so2538014iec.12 for ; Sun, 08 Feb 2015 05:17:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=HiVb+fujqiDYy8DYTx/Z83M79Sa+L2sc7xXEkR1JNv8=; b=mkRO9uifMEIU0ohqsqvyE+WjiA9yuHCYBd9o6Q2L31lC0qyuRJ6tO0lqzTbTPugG+m Pdn+Z5WCfZk6bAb1+iXysj117TYNiSwwh7PI21ewhigtGs4si+Y6hilca6zco8ybIkue grIjw4cEjIc36VfEpjYCMPP9eEcT3DBkExEaQd8vb35NkCmJ++0MPk7hYudX+kr+PWEG hrHipUgxVbGSbz5isl3rbFag96IGTz+pGEmJjpt7o+a9sDwJqiBBnCD+GkIKn9FZxOf4 QbBbmASKIgU13vA2Nu5nC8zZTlDu9IhTInBZE7Or6LgSqr/u0Iz2F7FTO9vvJbrVIiFO rspw== MIME-Version: 1.0 X-Received: by 10.42.64.193 with SMTP id h1mr21663024ici.32.1423401459331; Sun, 08 Feb 2015 05:17:39 -0800 (PST) Received: by 10.51.15.48 with HTTP; Sun, 8 Feb 2015 05:17:39 -0800 (PST) In-Reply-To: References: Date: Sun, 8 Feb 2015 08:17:39 -0500 Message-ID: Subject: Re: bloodhound ticket.create is producing funny tickets From: Olemis Lang To: user@bloodhound.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hi ! On 2/6/15, Ted wrote: > I've setup bloodhound (with sqllite) and the olemis-bloodhound-rpc plugin. > [...] > > I noticed that the xmlrpc created tickets are missing a product, I suspect > that's causing a problem, but I can't find any documentation on how to add > a product to a ticket. > I've seen this happening before . > The code I'm using to create a ticket is as follows : > > long time=System.currentTimeMillis(); > ArrayList params=new ArrayList<>(); > params.add("summary "+time); > params.add("description "+time); > > HashMap attributes=new HashMap(); > attributes.put("product", "DEF"); > params.add(attributes); > > Integer result = (Integer) client.execute("ticket.create", params); > I do not think this is an issue related to your code . > Does anyone know how to set the product on ticket.create? has anyone else > gotten ticket creation working over xmlrpc? Please consult the archive [1]_ for further clarification . .. [1] http://mail-archives.apache.org/mod_mbox/bloodhound-user/201401.mbox/%3C52CEF7D0.5090703@qwas.li%3E [...] -- Regards, Olemis - @olemislc Apache(tm) Bloodhound contributor http://issues.apache.org/bloodhound http://blood-hound.net Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: