Hi all, this is more of a conceptual question. I see that you can asscoiate a task with a requirement. Butfrom a conceptual point of view I think that tasks and requirements have a man-to-many relationship. The two requirements "Make app x faster" and "Make app y faster" might both be fulfilled by the task "Put app x on a different server than y". On the other hand a requirement like "Make app x faster" could also result in many tasks like "Review database access statements", "Use shared memory for..." etc. What is the idea in SpiraTeam to allow only ONE requirement to be associated with a task? Kind regards Werner 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/1232.aspxthreadId=1232Werner Alexi (alexi@alexi.de)associations Hi all, this is more of a conceptual question. I see that you can asscoiate a task with a requirement. Butfrom a conceptual point of view I think that tasks and requirements have a man-to-many relationship. The two requirements "Make app x faster" and "Make app y faster" might both be fulfilled by the task "Put app x on a different server than y". On the other hand a requirement like "Make app x faster" could also result in many tasks like "Review database access statements", "Use shared memory for..." etc. What is the idea in SpiraTeam to allow only ONE requirement to be associated with a task? Kind regards Werner Tue, 16 Jun 2015 12:34:59 -04002015-06-19T15:34:59-04:00/Support/Forum/spirateam/issues-questions/1232.aspxmessageId=2149Jim R (donotreply5@kronodesk.net) Hi Werner The idea is that a requirement (user story in Agile) is decomposed into many different Tasks that are needed to be completed to actually implement the desired feature. We don't allow many to many connections between requirements and tasks because the effort values from Tasks are aggregated to their parent Requirements. That would not be possible with many to many. For your example, we'd recommend creating two tasks, one for each app and then use the Task - Task associations to link them together. Regards Jim Fri, 19 Jun 2015 15:34:59 -04002015-06-19T15:34:59-04:00/Support/Forum/spirateam/issues-questions/1232.aspx#reply2149