You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <de...@bloodhound.apache.org> on 2013/07/23 15:25:13 UTC
[Apache Bloodhound] #608: Setting default_product in config causes
all tickets to be created in default_product.
#608: Setting default_product in config causes all tickets to be created in
default_product.
--------------------------+-------------------
Reporter: astaric | Owner:
Type: defect | Status: new
Priority: critical | Milestone:
Component: multiproduct | Version: 0.6.0
Keywords: |
--------------------------+-------------------
Setting default_product in [ticket] section in config sets default value
for product field in Ticket object to value from the config. Currently,
another value for product is inserted by the sql translator, resulting in
{{{
INSERT INTO (..., product, ..., product) VALUES (..., default_product,
..., active_product_prefix)
}}}
When this sql is executed on sqlite, the latest value is inserted into the
table, but the sql fails on Postgres and Mysql (see #601 and
[http://markmail.org/thread/xvbbqppktzmejszb mailing list]). After a fix
for #601 is applied, duplicated product fields will not be generated and
the ticket will be inserted with the wrong product.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/608>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #608: Setting default_product in config
causes all tickets to be created in default_product.
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#608: Setting default_product in config causes all tickets to be created in
default_product.
---------------------------+--------------------
Reporter: astaric | Owner:
Type: defect | Status: closed
Priority: critical | Milestone:
Component: multiproduct | Version: 0.6.0
Resolution: fixed | Keywords:
---------------------------+--------------------
Changes (by astaric):
* status: new => closed
* resolution: => fixed
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/608#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #608: Setting default_product in config
causes all tickets to be created in default_product.
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#608: Setting default_product in config causes all tickets to be created in
default_product.
---------------------------+---------------------
Reporter: astaric | Owner: astaric
Type: defect | Status: closed
Priority: critical | Milestone:
Component: multiproduct | Version: 0.6.0
Resolution: fixed | Keywords:
---------------------------+---------------------
Changes (by astaric):
* owner: => astaric
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/608#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #608: Setting default_product in config
causes all tickets to be created in default_product.
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#608: Setting default_product in config causes all tickets to be created in
default_product.
---------------------------+-------------------
Reporter: astaric | Owner:
Type: defect | Status: new
Priority: critical | Milestone:
Component: multiproduct | Version: 0.6.0
Resolution: | Keywords:
---------------------------+-------------------
Comment (by astaric):
Tickets created by qct do not suffer from this issues as default_product
is overriden with the value selected in the gui.
r1506038 adds current product as a hidden field to the newticket form.
Value from this field overrides the value set as default_product in
config.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/608#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker