DataStar Release: 2.4.3.5¶
Release Date: 21th August 2022
| Windows installer | Chocolatey |
|---|---|
| MSI Installer 2.4.3.5 | Choco DataStar 2.4.3.5 |
Dependencies¶
This release depends on Microsoft's .NET Framework 4.7.2 - this should be installed prior to upgrading. You can find the .NET Framework 4.7.2 by following these links:
Features¶
FEATURE 197 Support added for GIT SSH Known Hosts. DataStar will use ssh and ssh-keyscan if available to identify if the user has the GIT host configured in their SSH known hosts file. This check is performed when cloning a GIT repository via SSH and if required the user will be prompted with the option of adding the hostname to their known hosts file avoiding the need to have set this up previously.
Resolved Items¶
DEFECT 193 - Rally Task Tracking - An issue was identified where the User Interface allowed a User Story to be be entered when committing files to GIT, this resulted in an error when the user attempted to push the changes to GIT. The workaround was to perform the push from the command line if the user entered a story by mistake. This has now been fixed by two changes, firstly the push will not attempt to perform the commit associations if there is no SCM Repository configured, secondly the option to app a user story reference has been removed when using Rally where there is no SCM Repository configured.
DEFECT 194 - A issue has been identified that was allowing DataStar to be run more than once. Whilst this would be alerted as an error to the user a fix has now been applied so that only one instance of DataStar can be running. If the user tries to start a new instance the existing instance will be activated and the new instance will be stopped from running.
DEFECT 195 - The focus handling has been improved to help prevent occurrences of DataStar dropping into the background when closing some modal dialogs. The new behaviour will attempt to activate the existing a window when closing dialogs.
DEFECT 196 - An issue was identified where duplicate could be reported in the component view. This was caused by case sensitivity on the primary key when storing the list of components. A fix has been applied to ensure case is ignored when matching component names.