Inflectra Customer Forums: History of Requirement coverage and associations (Thread) I recently changed the requirement coverage of a testcase and was not able to find the change I just made in the artifact history. Associations are very relevant to my artifacts and I need to be able to monitor and retrace their history. For example anyone could delete all the associations of all artifacts of my project and no one could tell who it was or how many associations were deleted. Is there a way to get this history? Is this maybe a feature request? en-US(C) Copyright 2006-2024 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/2393.aspxthreadId=2393Pierre Alaplantive (pierre.alaplantive@tecmata.de)associations historyHistory of Requirement coverage and associations I recently changed the requirement coverage of a testcase and was not able to find the change I just made in the artifact history. Associations are very relevant to my artifacts and I need to be able to monitor and retrace their history. For example anyone could delete all the associations of all artifacts of my project and no one could tell who it was or how many associations were deleted. Is there a way to get this history? Is this maybe a feature request? Fri, 18 Jun 2021 07:05:31 -04002021-06-18T13:56:15-04:00/Support/Forum/spirateam/issues-questions/2393.aspxmessageId=3980David J (support1@inflectra.com) Yes. If you have SpiraTeam or SpiraPlan (not SpiraTest), and are running v6.9 or later you can use Yes. If you have SpiraTeam or SpiraPlan (not SpiraTest), and are running v6.9 or later you can use the Baselining feature. This lets you track association changes as well as just field changes: https://www.inflectra.com/SpiraTeam/Highlights/Baselining.aspx Regards David Fri, 18 Jun 2021 13:56:15 -04002021-06-18T13:56:15-04:00/Support/Forum/spirateam/issues-questions/2393.aspx#reply3980