Hi, currently I am subscribed to a lot of projects on our local SpiraTeam server. Since the list is now longer than my screen is able to display, I descided to unsubscribe from some old projects (that are still used, but not by me!). First though was to remove me as a user from the project (using the Project Membership page). If another user now opens a incident (for example) where my name is used (on the field Detected By for example), this field is set to None. This is of course undesired behaviour. Is there a way to hide some entries in the project list (at the top of the SpiraTeam website, the dropdown box), without interfering with the current content of the project? 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/issues-questions/772.aspxthreadId=772Stefan van Loenhout (svloenhout@huisman-nl.com)subscriptions Hi, currently I am subscribed to a lot of projects on our local SpiraTeam server. Since the list is now longer than my screen is able to display, I descided to unsubscribe from some old projects (that are still used, but not by me!). First though was to remove me as a user from the project (using the Project Membership page). If another user now opens a incident (for example) where my name is used (on the field Detected By for example), this field is set to None. This is of course undesired behaviour. Is there a way to hide some entries in the project list (at the top of the SpiraTeam website, the dropdown box), without interfering with the current content of the project? Fri, 29 Nov 2013 11:05:55 -05002014-01-24T13:01:38-05:00/Support/Forum/spirateam/issues-questions/772.aspxmessageId=1403Jim R (donotreply5@kronodesk.net)Hi Stefan I'm afraid that if you remove yourself from the Project Membership you will no longer appear in the various dropdown lists for that project. It won't affect any historical data, but if someone edits an incident/requirement/testcase/etc. it will require them to choose a new name from the list. Regards Jim Fri, 29 Nov 2013 13:16:56 -05002013-11-29T13:16:56-05:00/Support/Forum/spirateam/issues-questions/772.aspx#reply1403messageId=1406Stefan van Loenhout (svloenhout@huisman-nl.com) Ok, thank you for the information.Mon, 02 Dec 2013 09:32:12 -05002013-12-02T09:32:12-05:00/Support/Forum/spirateam/issues-questions/772.aspx#reply1406messageId=1478Dennis Weisgram (dmweisgram@aol.com) Jim, As the Spira Admin, I have the same issue.The active list is pretty long. However, Stefan brings up a good point about the "undesired behaviour" when users are inactivated, but their name is associated to an artifact. We have locked down the detector in our workflow so that it isn't "accidentally" altered by a user. So when someone leaves, I have reassign their incidents to another user. It can be time consuming with really large projects. I would rather have it retain an inactive users, then switch to (none). Thu, 23 Jan 2014 23:33:27 -05002014-01-23T23:33:27-05:00/Support/Forum/spirateam/issues-questions/772.aspx#reply1478messageId=1484Vanessa Smith (vanessa.smith@flhosp.org) Jim, We too have found this behavior undesirable. It's fine to not have active users in the drop-down, but why force us to change data that was correct when it was first entered there? I feel the fields should only force validation if data was changed in them, not just that the record was changed. Thanks, Fri, 24 Jan 2014 13:01:38 -05002014-01-24T13:01:38-05:00/Support/Forum/spirateam/issues-questions/772.aspx#reply1484