Assignment of releases to requirements/test cases/defects

Options
Christoph L
Christoph L Member Posts: 7
edited August 2016 in

Currently an item can be assigned to one
release only.

Multiple value for the attribute ‘Release’ is a must-have for our company because the failure tracking tool (JIRA) in use for the related mapped attributes are multiple value.

Currently we sync them only once, but this would not allow us to use JAMA defects as flexible as we wanted to.

Same applies for attribute ‘affects Version’ for item type ‘defect’.


Additional info:

As this question have already been taken into account within the Q&A section of Test Center Webinar, I would now like you to consider this as a feature.

Comments

  • [Deleted User]
    [Deleted User] Posts: 911
    edited June 2016
    Options
    Christoph, this is definitely something that would make sense to add, especially considering you are using JIRA for tracking defects and it supports multiple releases.

    For users that are not syncing to JIRA, the best workaround we can suggest for this issue is to create an item type called "Release," which could then have features, requirements, defects, etc. related downstream from it.
  • Matjaz Nartnik
    Matjaz Nartnik Member Posts: 3
    edited June 2016
    Options
    Is this feature added to roadmap? We ahve teh same situation as described by Cristhoph. Release field is becoming practicaly unusable.
  • [Deleted User]
    [Deleted User] Posts: 911
    edited June 2016
    Options
    Hi Matjaz. At this point, this feature is not on the road map. 

Categories