Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of ryan.ollos@wandisco.com
 designates 209.85.223.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAHM0gniz24s-L90aY7QecO8Rxo1ozh03KUL3p421_pdSFtktEQ@mail.gmail.com>
References: <056.1430e7942807e4344d5414b567d49832@incubator.apache.org>
	<071.13a9eb999fb3def7897e3adbf42500d3@incubator.apache.org>
	<CAHM0gniz24s-L90aY7QecO8Rxo1ozh03KUL3p421_pdSFtktEQ@mail.gmail.com>
Date: Tue, 18 Dec 2012 17:10:57 -0800
Message-ID: 
 <CAPt9QwT1ceRoxF0sAs3nrv741W364Cems7CMvu5F2FJwrT1BPg@mail.gmail.com>
Subject: Re: [Apache Bloodhound] #304: Default product is not the default
 option in the ticket quick create or newticket form
From: Ryan Ollos <ryan.ollos@wandisco.com>
To: bloodhound-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=f46d0447a251714a5f04d12a49dd

--f46d0447a251714a5f04d12a49dd
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Dec 17, 2012 at 12:52 AM, Andrej Golcov <andrej@digiverse.si> wrote:

> Is this ticket intercepted with BEP-0003 (MultiProduct)?
>

It could be fixed as part of the BEP-0003 implementation, or the ticket
could be completely irrelevant if this part of the current multi-product
implementation is thrown out and replaced in the course of  implementing
BEP-0003. I raised the ticket because it is a broken feature in the current
bloodhound release, and the current ITicketFieldProvider would most likely
need to be extended in order to fix it.


> As far as I understand, in multiproduct environment ticket product
> will be defined by property in current environment?
>

I was thinking that the Quick Create Ticket and New Ticket forms will still
be at global scope, and therefore a product will need to be selected in the
form for both cases. I've only skimmed over BEP-0003 though, so I wouldn't
be surprised if I missed something that spoke to this.

--f46d0447a251714a5f04d12a49dd--