When creating a bug/change request/enhancement/incident/issue/limitation/risk it would be very useful to be able performing a multiple assignment (as known from Polarion). In case of uncertainty who is correct owner/recipient of a certain defect and to avoid rerouting loops, it is needed to address the defect to several potential owner of the defect. 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/spiratest/issues-questions/2030.aspxthreadId=2030Andreas Haselow (andreas.post@mail.de) When creating a bug/change request/enhancement/incident/issue/limitation/risk it would be very useful to be able performing a multiple assignment (as known from Polarion). In case of uncertainty who is correct owner/recipient of a certain defect and to avoid rerouting loops, it is needed to address the defect to several potential owner of the defect. Wed, 22 May 2019 10:59:42 -04002019-05-22T20:11:02-04:00/Support/Forum/spiratest/issues-questions/2030.aspxmessageId=3588Jim R (donotreply5@kronodesk.net) Hi Andreas, We deliberately have a single Owner so that there is a single point of accountability: https://www.inflectra.com/Ideas/Entry/one-throat-to-choke--why-we-only-allow-one-owner-305.aspx However you can have Followers (using the Subscribe > Add Follower button) that lets you have additional non-primary owners. Alternatively you can add additional User custom property types. Regards Jim Wed, 22 May 2019 20:11:02 -04002019-05-22T20:11:02-04:00/Support/Forum/spiratest/issues-questions/2030.aspx#reply3588