Re: [Apache Bloodhound] #647: Can't reassign ticket to another product once assigned to Default (@) product
#647: Can't reassign ticket to another product once assigned to Default (@) product ---+ Reporter: ChrisHarris | Owner: nobody Type: defect| Status: new Priority: major | Milestone: next 0.x Component: multiproduct |Version: 0.6.0 Resolution:| Keywords: ticket product ---+ Comment (by rjollos): Feature request made on the [http://markmail.org/message/nv3bo5efntqvwz34 mailing list]. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/647#comment:5 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #647: Can't reassign ticket to another product once assigned to Default (@) product
#647: Can't reassign ticket to another product once assigned to Default (@) product ---+ Reporter: ChrisHarris | Owner: nobody Type: defect| Status: new Priority: major | Milestone: next 0.x Component: multiproduct |Version: 0.6.0 Resolution:| Keywords: ticket product ---+ Changes (by rjollos): * milestone: = next 0.x -- Ticket URL: https://issues.apache.org/bloodhound/ticket/647#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #647: Can't reassign ticket to another product once assigned to Default (@) product
#647: Can't reassign ticket to another product once assigned to Default (@)
product
---+
Reporter: ChrisHarris | Owner: nobody
Type: defect| Status: new
Priority: major | Milestone:
Component: multiproduct |Version: 0.6.0
Resolution:| Keywords:
---+
Changes (by astaric):
* owner: = nobody
* component: = multiproduct
Comment:
We are aware that there is currently no automatic way to transfer tickets
between products. There is currently an open proposal concerning ticket
id-s (Proposals/BEP-0010) that needs to be implemented before we can start
working on transferring tickets between products.
Meanwhile, manually changing the product field in the database should
work, but you need to be careful, to also modify related tables
(ticket_change, ticket_custom, attachment, bloodhound_relations).
Search index update will not be triggered, if you modify data directly, so
you should do it manually by running
{{{
trac admin path/to/your/env bhsearch rebuild
}}}
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/647#comment:1
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #647: Can't reassign ticket to another product once assigned to Default (@) product
#647: Can't reassign ticket to another product once assigned to Default (@) product ---+ Reporter: ChrisHarris | Owner: nobody Type: defect| Status: new Priority: major | Milestone: Component: multiproduct |Version: 0.6.0 Resolution:| Keywords: ---+ Comment (by olemis): Replying to [ticket:647 ChrisHarris]: [...] 4.) Locate the newly created ticket and click on Modify Ticket. You can't reassign the ticket to another product. The ticket is stuck as being associated with @. This is a very annoying problem. I've tried manually changing the ticket's product association in PostgreSQL, but that causes an even bigger problem (The ticket will appear via Search and Tickets, but clicking on the ticket will result in an error page). Changing ticket product in ticket UI is not supported . Nevertheless you can - click ''Tickets'' menu item to go to the dashboard - click ''Custom Query'' to go to query form - select target tickets - expand batch modify box - in ''Add field'' combo box select ''Product'' - select an existing product prefix . - input comment (optional) - click ''Change ticket'' button to commit your changes That has worked for me before ... I use this to move spam to an special [http://blood-hound.net/products/trash trash] product . Please let us know if that will work for you . Should you find any issues we'd like to know about the details . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/647#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #647: Can't reassign ticket to another product once assigned to Default (@) product
#647: Can't reassign ticket to another product once assigned to Default (@) product ---+ Reporter: ChrisHarris | Owner: nobody Type: defect| Status: new Priority: major | Milestone: Component: multiproduct |Version: 0.6.0 Resolution:| Keywords: ticket product ---+ Changes (by olemis): * keywords: = ticket product -- Ticket URL: https://issues.apache.org/bloodhound/ticket/647#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] #647: Can't reassign ticket to another product once assigned to Default (@) product
#647: Can't reassign ticket to another product once assigned to Default (@) product --+- Reporter: ChrisHarris |Owner: Type: defect | Status: new Priority: major| Version: 0.6.0 Resolution: | --+- Windows Server 2008 Waterfox v18.0.1 Bloodhound v0.7.0 Python v2.7.5 SetupTools v0.98 PostgreSQL v9.2 as back end Apache HTTPd v2.2 as front end 1.) After having done a fresh install of Apache Bloodhound 0.7.0 and created additional Products from the Admin page (and that's all), Click on Create Ticket from the Home page. 2.) Leave the ticket as assigned to @, which is the default product assignment. 3.) Click on Create. 4.) Locate the newly created ticket and click on Modify Ticket. You can't reassign the ticket to another product. The ticket is stuck as being associated with @. This is a very annoying problem. I've tried manually changing the ticket's product association in PostgreSQL, but that causes an even bigger problem (The ticket will appear via Search and Tickets, but clicking on the ticket will result in an error page). -- Ticket URL: https://issues.apache.org/bloodhound/ticket/647 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
