Inflectra Customer Forums: Releases, Associations tab, proposal (Thread) Currently it is not allowed to associate with releases any enities, it is possible only include them using release field. But sometimes more flexibility is needed. I want to be able to associate with releases any spira entities including tasks (and releases from other projects) from any project (release could be in project A, while task could be from project B). This will allow me to create projects for the lets say customer-related. Use-case: I have projects for internal, product-development acitivities. They have own release naming. When we deploy a new version to a customer it has its own naming convension, where other entities (all types incl other releases and independant tasks) may be added with multiple-to multiple relations. As you already have Associations tab, it wont take long to add what is already developed to a one more entity but it defenitily will be a huge step towards good relationships between Inflectra and their customers. 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/2468.aspxthreadId=2468Ilia Poliakov (ilya.polyakov@edetek.com)Releases Associations proposalReleases, Associations tab, proposal Currently it is not allowed to associate with releases any enities, it is possible only include them using release field. But sometimes more flexibility is needed. I want to be able to associate with releases any spira entities including tasks (and releases from other projects) from any project (release could be in project A, while task could be from project B). This will allow me to create projects for the lets say customer-related. Use-case: I have projects for internal, product-development acitivities. They have own release naming. When we deploy a new version to a customer it has its own naming convension, where other entities (all types incl other releases and independant tasks) may be added with multiple-to multiple relations. As you already have Associations tab, it wont take long to add what is already developed to a one more entity but it defenitily will be a huge step towards good relationships between Inflectra and their customers. Mon, 23 Aug 2021 08:06:01 -04002022-12-16T06:31:59-05:00/Support/Forum/spirateam/issues-questions/2468.aspxmessageId=4073Dmitriy Andropov (andropovdv@gmail.com) The same question is vary actual for my company. Looking forward for the clarifications and furthe The same question is vary actual for my company. Looking forward for the clarifications and further updates. Mon, 23 Aug 2021 08:15:53 -04002021-08-23T08:15:53-04:00/Support/Forum/spirateam/issues-questions/2468.aspx#reply4073messageId=4085David J (support1@inflectra.com) We have a plan to add Release as a new type of custom property, similar to what we have for users. We have a plan to add Release as a new type of custom property, similar to what we have for users. Mon, 23 Aug 2021 11:37:01 -04002021-08-23T11:37:01-04:00/Support/Forum/spirateam/issues-questions/2468.aspx#reply4085messageId=4088Ilia Poliakov (ilya.polyakov@edetek.com) David , that is good, but not enough. What if the same internal release from a core-projects is g David , that is good, but not enough. What if the same internal release from a core-projects is going to be delivered through several different customers releases (to be more precise, to different customers, so names of the release could be different)? So, I need to have an option how to make multiple-to-mutliple mapping for any project and any entity. Example: We have developed feature Perfect in our core project during Sprint 13/component Release 1.2.5. That will go to customer A in release 1. (for tracking what happens with customer A, we have a dedicated spira project customer A with their own releases) The same component will go to customer B in release 2. (for tracking what happens with customer B, we have a dedicated spira project customer B with their own releases) If we try to solve it via custom fields we need to create amount of custom fields equal to amount of customers, that is crazy. Having ability to associate release/sprint with any entity in any project will solve our problem, moreover it doesnt look difficult as it was already developed by Inflectra to other entities. Mon, 23 Aug 2021 12:42:34 -04002021-08-23T12:42:34-04:00/Support/Forum/spirateam/issues-questions/2468.aspx#reply4088messageId=4090David J (support1@inflectra.com) Having the ability to associate any artifact to a release would be relatively straightforward. The Having the ability to associate any artifact to a release would be relatively straightforward. The once concern is that for those artifacts that already have dedicated Releases tabs (e.g. test cases) it would be confusing, since the Associations tab would be for linking, without causing any business rules to take place whereas the main Releases tab is used for calculating things like test coverage, test progress, etc. Mon, 23 Aug 2021 13:14:18 -04002021-08-23T13:14:18-04:00/Support/Forum/spirateam/issues-questions/2468.aspx#reply4090messageId=4091Ilia Poliakov (ilya.polyakov@edetek.com) Yep, that is normal. All built-in mechanism: Releases tab is used for calculating things like tes Yep, that is normal. All built-in mechanism: Releases tab is used for calculating things like test coverage, test progress, etc. should have the some logic from Inflectras side as how it is built now. It shouldnt recieve any influence from my associations. What I will additionally link - it is my responsibility how to interpret it. I do not expect any calculations from Inflectras side, just create and show that association in the Associations tab for the Release and associated entity. So, I expect two mechanism: what is currently built in with its default logic, calculations, etc. using special release-fields (Planned relaese, Relaese, etc.) and that additional linkeage and there it is my responsibility how to use it ( I am going to use it via custome reports). Mon, 23 Aug 2021 13:54:23 -04002021-08-23T13:54:23-04:00/Support/Forum/spirateam/issues-questions/2468.aspx#reply4091messageId=4092Ilia Poliakov (ilya.polyakov@edetek.com) Probably, we need to consider that proposal wider: to let user assoiciate any Spira entity to any t Probably, we need to consider that proposal wider: to let user assoiciate any Spira entity to any through any project. For example, to let associations be from tasks in project A to a requirement in project B (currently it is forbidden I dont know why) and etc. All these assoications shouldnt require any calculations or logic from Spiras side, meaning of association should be an users area of responsibility. Mon, 23 Aug 2021 14:31:47 -04002021-08-23T14:31:47-04:00/Support/Forum/spirateam/issues-questions/2468.aspx#reply4092messageId=4160Dmitriy Andropov (andropovdv@gmail.com) Hi David, please let us know if there any updates for the request? Hi David, please let us know if there any updates for the request? Tue, 26 Oct 2021 13:25:36 -04002021-10-26T13:25:36-04:00/Support/Forum/spirateam/issues-questions/2468.aspx#reply4160messageId=4241Ilia Poliakov (ilya.polyakov@edetek.com) Are there any news when it is going to be implemented? Are there any news when it is going to be implemented? Wed, 19 Jan 2022 08:11:12 -05002022-01-19T08:11:12-05:00/Support/Forum/spirateam/issues-questions/2468.aspx#reply4241messageId=4252Ilia Poliakov (ilya.polyakov@edetek.com) As release-type custom field is going to be added in a future versions, multiselect release-type cu As release-type custom field is going to be added in a future versions, multiselect release-type custom field might relieve me with my pain. Probably, it is easier for you to implement such way (in comparison allow to associate releases). I really need it. Thank you. Wed, 19 Jan 2022 10:23:34 -05002022-01-19T10:23:34-05:00/Support/Forum/spirateam/issues-questions/2468.aspx#reply4252messageId=5827Ilia Poliakov (ilya.polyakov@edetek.com) Hello, are there any news about: Allowing associations with releases (no other logic needed). As Hello, are there any news about: Allowing associations with releases (no other logic needed). As it is done with incidents that they could be associated. Adding new custom field type: releases with MultiSelect Fri, 16 Dec 2022 06:31:59 -05002022-12-16T06:31:59-05:00/Support/Forum/spirateam/issues-questions/2468.aspx#reply5827