Skip Navigation LinksHome Page > Forums > SpiraTeam Forums > SpiraTeam Issues & Questi... > Builds, how to link requi...
Hi Spira Support,
It is possible to link tasks and requirements into builds? Based on Available Database Tables - SpiraDocs (inflectra.com) I can see that incident may have a build, but no such attributes for tasks and requirements. And we need to track not only incidents, we need to know how requirements and tasks are grouped into builds.
Another question that in real life we have multiple to multiple relationship between builds and other entities like incidents and tasks. We have dedicated builds that we are supporting for each of our clients and we need to know was that incident/task deployed to their release. So one incident goes to several builds that may be associated to several different release in Spira (when our customers use different versions of our product).
The link is done implicitly via commits:
David, Thanks for your answer!
Could you provide step by step examples as we would like to synthetically reproduce that logic using Spira's APIs? We are using Amazon code commit that you are not supporting yet.
So, I need to know step by step what entities should I create with what associations, etc. Better with names of API calls that I should use.
OK, for AWS CodeCommit (which is on our list now that we have done GitLab, GitHub and CircleCI). You need to call this Build API:
The list of commits is very important, basically this JSON:
And forgot to mention, the commits inside Git need to have their message include the appropriate Spira token [IN:5], [RQ:2] etc.
Great! I am glad to hear that AWS CodeCommit will be supported by Inflectra. We will wait for it.
And if you have any questions, please email or call us at +1 (202) 558-6885