Inflectra Customer Forums: Builds, how to link requirements into builds? (Thread) 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). en-US(C) Copyright 2006-2024 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/2674.aspxthreadId=2674Ilia Poliakov (ilya.polyakov@edetek.com)BuildsBuilds, how to link requirements into builds? 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). Fri, 02 Sep 2022 14:03:44 -04002022-09-23T11:55:08-04:00/Support/Forum/spirateam/issues-questions/2674.aspxmessageId=5729David J (support1@inflectra.com) The link is done implicitly via commits: The CI build (from the CI tool such as Jenkins, GitLab, The link is done implicitly via commits: The CI build (from the CI tool such as Jenkins, GitLab, etc.) contains code commits (Git) or revisions (SVN) The code commits have artifact tags such [TK:45] or [RQ:23] the code commits are then linked to the requirements and tasks The builds are linked via. the commits to the requirements and tasks Fri, 02 Sep 2022 20:25:45 -04002022-09-02T20:25:45-04:00/Support/Forum/spirateam/issues-questions/2674.aspx#reply5729messageId=5730Ilia Poliakov (ilya.polyakov@edetek.com) David, Thanks for your answer! Could you provide step by step examples as we would like to synthet David, Thanks for your answer! Could you provide step by step examples as we would like to synthetically reproduce that logic using Spiras 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. Mon, 05 Sep 2022 07:02:08 -04002022-09-05T07:02:08-04:00/Support/Forum/spirateam/issues-questions/2674.aspx#reply5730messageId=5738David J (support1@inflectra.com) Hi Ilya OK, for AWS CodeCommit (which is on our list now that we have done GitLab, GitHub and Circ Hi Ilya 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: https://api.inflectra.com/Spira/Services/v6_0/RestServiceOperation.aspx?uri=projects%2f%7bproject_id%7d%2freleases%2f%7brelease_id%7d%2fbuilds&method=POST The list of commits is very important, basically this JSON: "Revisions": [ { "RevisionKey": "44bf09d0a2c36585aed1c34ba2e5d958a9379718" }, { "RevisionKey": "44bf09d0a2c36585aed1c34ba2e5d958a9379718" } ] Thu, 22 Sep 2022 15:42:49 -04002022-09-22T15:42:49-04:00/Support/Forum/spirateam/issues-questions/2674.aspx#reply5738messageId=5739David J (support1@inflectra.com) And forgot to mention, the commits inside Git need to have their message include the appropriate Sp And forgot to mention, the commits inside Git need to have their message include the appropriate Spira token [IN:5], [RQ:2] etc. Thu, 22 Sep 2022 15:43:44 -04002022-09-22T15:43:44-04:00/Support/Forum/spirateam/issues-questions/2674.aspx#reply5739messageId=5740Ilia Poliakov (ilya.polyakov@edetek.com) Great! I am glad to hear that AWS CodeCommit will be supported by Inflectra. We will wait for it. Great! I am glad to hear that AWS CodeCommit will be supported by Inflectra. We will wait for it. Fri, 23 Sep 2022 05:25:43 -04002022-09-23T05:25:43-04:00/Support/Forum/spirateam/issues-questions/2674.aspx#reply5740messageId=5741David J (support1@inflectra.com) Youre welcome.! Youre welcome.! Fri, 23 Sep 2022 11:55:08 -04002022-09-23T11:55:08-04:00/Support/Forum/spirateam/issues-questions/2674.aspx#reply5741