Associations between Tasks and Requirements

Wednesday, March 16, 2022
Avatar

We are trying to create a dependency matrix (critical path) using Spira's 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.

4 Replies
Wednesday, March 16, 2022
Avatar
re: ilyapolyakov Wednesday, March 16, 2022

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.

 

Wednesday, March 16, 2022
Avatar
re: inflectra.david Wednesday, March 16, 2022

David, thanks for an answer but for technical activities like deployments, etc. we shouldn't have requirements.

So your receipe deasn't work. Please add an option to associate tasks and requirements through associations.

Saturday, March 19, 2022
Avatar
re: ilyapolyakov Wednesday, March 16, 2022

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.

Monday, March 21, 2022
Avatar
re: inflectra.david Saturday, March 19, 2022

David, Thanks for your suggestion, but unfortunately it doesn't 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.

Statistics
  • Started: Wednesday, March 16, 2022
  • Last Reply: Monday, March 21, 2022
  • Replies: 4
  • Views: 331