Xsquash4Jira Plugin Release Notes
5.0.1
Released on 2023/04/18
Compatible with Squash TM 5.X
Corrections
- 9109 Synchronization of user stories fails if the high level requirement is not found
- 9110 Synchronization of epics fails if links between requirements are synchronized
5.0.0
Released on 2023/03/07
Compatible with Squash TM 5.X
Evolutions
- Synchronization of Jira epics as Squash high level requirements
- Synchronization of epic - user story Jira links as high level requirement - standard requirement Squash links
- Indication of tickets synchronized several times in the UI and logs
- Resizing of the columns of the Synchronizations block
- Improve the validation of YAML configurations
Corrections
- 8743 Display of the preview of images inserted in the description of Jira Cloud tickets is broken
- 8934 Incorrect synchronization of a board from a team managed project
- Folder creation fails if the project name contains a slash
- An incomplete YAML syntax leads to a synchronization failure
- Impossible to modify mappings in a template if a synchronization of an associated project is disabled
4.1.1
Released on September 6, 2023
Compatible With Squash TM 4.1
Corrections
- NullPointerException on synchronizations due to addition of 'parent' field on all Jira Cloud tickets
4.1.0
Released on November 9, 2022
Compatible with Squash TM 4.1
Evolutions
- Support of OAuth 2 protocol for Squash-Jira communication
Corrections
- The "Disable the plugin" popup is not displayed for a project template
- Forcing the synchronization of a disabled synchronization does not return an error
- Synchronization failure when the name of a link between requirements has a "/"
- Issue when displaying the servers list on the campaign wizard
4.0.0
Released on July 28 2022
Compatible with Squash TM 4.0
Evolutions
- Compatibility with Squash TM 4.0
- Limit permissions of Xsquash4Jira synchronizations
- Add project_id and project_name fields in the API GET synchronization response
- Reduce the volume of logs about Jira reporting by modifying the logger level from warn to debug
Corrections
- Bad mangament of duplicate tickets in the Execution Plan Designer
- 8854 Execution Plan Designer not available
- Coverage indicators calculation incoherent when the same tickets are synchronized several times with the same server
- Display issue in the Execution Plan Designer if there are duplicate sprints or versions
- Milestones linked to synchronized requirements are lost when the synchronization occurs
- The Exection Plan Designer does not take into account credentials on Squash TM projects
3.0.1
Released on September 6, 2023
Compatible With Squash TM 3.X
Corrections
- NullPointerException on synchronizations due to addition of 'parent' field on all Jira Cloud tickets
3.0.0
Released on December 17, 2021
Compatible With Squash TM 3.X
Evolutions
- Add API documentation links in the "Help" menu of the navigation bar
- Upgrade of API version from 2 to latest
Corrections
- Reporting fields are not updated if an issue has been moved
- Requirements creation date is modified after a synchronization
- Issues when the browser language is set in Italian
2.1.0
Released on August 26, 2021
Compatible with Squash TM 2.1
Evolutions
- Xsquash4Jira's configuration is now taken into account in project templates, which consequently applies to linked projects as well;
- In the tree and in the requirements' consultation page, the synchronization status of the linked Jira issue (synced, unsynced, or deleted in Jira) is now displayed;
- An option was added to simulate a synchronization in order to view the number and details of the tickets it contains before adding it;
- A button was added to refresh the "Synchronizations" block on the configuration page of the Xsquash4Jira plugin;
- The display of syntax errors during the configuration of equivalences between field values was improved.
Corrections
- A filter containing an apostrophe makes the synchronization fail.
2.0.0
Released on July 1st, 2021
Compatible with Squash TM 2.0
Evolutions
- Compatible with Squash TM 2.0
- Force mass synchronization
Corrections
- Sprints are not recovered during a table sync, in the new generation projects with Jira Cloud.