We are trying to create a dependency matrix (critical path) using Spiras associations (depends on with the comment one of SS, FS, FF, SF) but currrently it is NOT possible to associate tasks and requirements. Why is it important? We may have business-requirements and a task after a requirements (for example deployment) that has a dependency FS on business-requirements but currently is is not possible to associate tasks and requirements. 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/2587.aspxthreadId=2587Ilia Poliakov (ilya.polyakov@edetek.com)associations We are trying to create a dependency matrix (critical path) using Spiras associations (depends on with the comment one of SS, FS, FF, SF) but currrently it is NOT possible to associate tasks and requirements. Why is it important? We may have business-requirements and a task after a requirements (for example deployment) that has a dependency FS on business-requirements but currently is is not possible to associate tasks and requirements. Wed, 16 Mar 2022 08:03:20 -04002022-03-21T08:26:26-04:00/Support/Forum/spirateam/issues-questions/2587.aspxmessageId=4291David J (adam.sandman+support@inflectra.com) You can create Tasks under requirements Just go to a specific requirement and in the Tasks tab create the tasks. Alternatively you go to a Task and link to a requirement. It is a one to many association. Wed, 16 Mar 2022 12:34:44 -04002022-03-16T12:34:44-04:00/Support/Forum/spirateam/issues-questions/2587.aspx#reply4291messageId=4292Ilia Poliakov (ilya.polyakov@edetek.com) David, thanks for an answer but for technical activities like deployments, etc. we shouldnt have requirements. So your receipe deasnt work. Please add an option to associate tasks and requirements through associations. Wed, 16 Mar 2022 14:08:17 -04002022-03-16T14:08:17-04:00/Support/Forum/spirateam/issues-questions/2587.aspx#reply4292messageId=4294David J (adam.sandman+support@inflectra.com) I would recommend you simply create tasks under the requirements for the requirement activities. Then for the other ancillary tasks (e.g. deployments), you associate those tasks with the requirement tasks. Sat, 19 Mar 2022 13:11:51 -04002022-03-19T13:11:51-04:00/Support/Forum/spirateam/issues-questions/2587.aspx#reply4294messageId=4295Ilia Poliakov (ilya.polyakov@edetek.com) David , Thanks for your suggestion, but unfortunately it doesnt work: We can not create requirements for ongoing activities. As we are FDA-compliant, requirements are included to many compliance docs where all requirements should be completed once they are done. So we can not create one requirement Deployment and create deployment-tasks under it and reopen that requirement each time we have a deployment activity (having a completed requirement with not finished task under it is forbidden and will be a finding during any audit). So if to follow you advice, we should have one requirement for any new deployment and it is a mess as we have thousands of deployments during a month. And moreover that situation is normal (as for me, it is a nature of tasks as a separate entity): we can have tasks that are not related to any requirement, thay may be related to a release or to any other entity. Mon, 21 Mar 2022 08:26:26 -04002022-03-21T08:26:26-04:00/Support/Forum/spirateam/issues-questions/2587.aspx#reply4295