In addition to fixing a number of bugs, improvements and new features have been implemented in the JIRA linkage in this release. More information about the standard JIRA coupling can be found here.
defect With relationship to JIRA issue move to other Test cycle
When a defect that has a relationship to a JIRA issue is moved to another Test cycle within Testersuite it will be handled as follows as of this release:
- If the Test cycle in Testersuite to which the defect is moved has a relationship with the JIRA project to which the JIRA issue belongs then the relationship between the Testersuite defect and the JIRA issue is maintained.
- If the Test cycle in Testersuite to which the defect is moved has no relationship to the JIRA project to which the JIRA issue belongs then the relationship between the Testersuite defect and the JIRA issue is severed.
In the details of a Test cycle , the relationship to a JIRA project can be changed if necessary.
Issue with a relation to a Testersuite defect is removed in JIRA
When an issue is deleted in JIRA, this is now also reflected in Testersuite. A check is made to see if there is a Testersuite defect related to the JIRA issue. If that is the case, the relationship with the JIRA issue will be removed in this defect . The defect itself will not be removed.
User-story with a relation to a Testersuite requirement is deleted in JIRA
When a user story is deleted in JIRA, this is now also reflected in Testersuite. A check is made to see if there is a Testersuite requirement related to the user story. If that is the case, the relationship with the JIRA user story will be removed. The requirement itself will not be removed.