Skip Navigation LinksHome Page > Forums > SpiraTeam Forums > SpiraTeam Best Practices > What is the best way to r...
We have situations where portions of the work needed can satisfy multiple requirements.
For example, two Reports were requested by the business and each was entered as a separate requirement. We have database development tasks and Crystal Reports development tasks necessary for each. In this case, the database work will be done in one shot but it will support both Requirements. I don't think two requirements can point to the same task. Our choices seem to be to pick one of the requirements and add the task there; or, duplicate the task in both (not desirable); or, just have the task not be connected to any requirement (and just a release), which is also not desirable.
Any thoughts out there on how we could better relect this work in Spira?
Due to the way the system rolls up effort and progress to requirements, it does not allow a single task to be linked to more than one requirement at present. Generally we'd recommend trying to have the unique work for each requirement be its own task (i.e. the database and crystal reports for Req #1 as one set of task and the database and crystal reports for Req #2 as a separate set of tasks).