We use SpiraTeam to manage our projects, but we would also like to set up a general portal for bug tracking, where any employee can report an issue, without having to be a member of a particular project ahead of time. The user should be able to maintain visibility on the status of the incident as it moves through the system. Our current idea is to set up a "general" SpiraTeam project where all employees are members. A manager would periodically review entered bugs and copy them to the appropriate project for the team to review. The problem with this is that the original bug that has public visibility would not be updated as the copied incident is changed over time. Are there any recommendations for best practices around this scenario? Is a third-party bug tracking tool our only option here? Thanks in advance for any input. en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/best-practices/642.aspxthreadId=642Greg Ferreri (gferreri@glneurotech.com)We use SpiraTeam to manage our projects, but we would also like to set up a general portal for bug tracking, where any employee can report an issue, without having to be a member of a particular project ahead of time. The user should be able to maintain visibility on the status of the incident as it moves through the system. Our current idea is to set up a "general" SpiraTeam project where all employees are members. A manager would periodically review entered bugs and copy them to the appropriate project for the team to review. The problem with this is that the original bug that has public visibility would not be updated as the copied incident is changed over time. Are there any recommendations for best practices around this scenario? Is a third-party bug tracking tool our only option here? Thanks in advance for any input. Tue, 16 Jul 2013 19:27:44 -04002013-07-17T17:37:50-04:00/Support/Forum/spirateam/best-practices/642.aspxmessageId=1174David J (adam.sandman+support@inflectra.com) Hi Greg Generally if it's a product bug, then the usual process is for the user to log the bugs in the project that corresponds to the product that has the issue. For general customer issues/tickets, we'd recommend using our KronoDesk product that is a general purpose help-desk tool that can then create incidents in SpiraTeam when a particular ticket reaches the point that you know which product it affects and a system defect needs to be logged. Regards Adam Wed, 17 Jul 2013 17:37:50 -04002013-07-17T17:37:50-04:00/Support/Forum/spirateam/best-practices/642.aspx#reply1174