We added a new link editor: The Bulk link creation editor facilitates fast link creation by a simple drag-and-drop mechanism.
In order to find the relevant artifacts in your particular case, the Bulk link creation editor also supports general text filters as well as attribute specific filters which can be defined for particular columns.
In order to optimize the performance of DOORS data retrieval of YAKINDU Traceability, we now offer two data extraction strategies
Background: For larger projects, we ran into situations with the DOORS client stating „Memory exhausted”. It was simply not possible to extract all data in one run. Therefore, we now offer the above option – together with the established option to „always reload DOORS on startup” you can configure the DOORS data extraction strategy to optimal performance with regards to your project size.
It is now possible to navigate from YAKINDU Traceability to Polarion by means of a doubleclicking the representative of the Polarion work item in YT.
On doubleclick, YT opens the browser with an URL directly pointing to the Polarion work item.
Note: In order to use this feature, you may want to adjust the configuration of the Polarion data access in order to give YT a hint regarding the Polarion base URL.
We improved the hover feedback when dragging artifacts into text editors or C/C+editors. YT gives now better guidance whether the current cursor position is a valid drop location.
We changed the pattern of the description of issues which were revealed by YT validations (e.g. suspicious links, missing artifacts).
The old pattern was Artifact + Kind of Issue . This made it hard to seach for issues by kind, especially in cases when only a part of the description was visible. In order to improve the usability in this case, we changed the pattern to Kind of Issue + Artifact
In order to overcome potential misunderstandings regarding duplicate elements in unions of query results, we added a new query function
As a rule of thump, keep in mind that the following:
- union : duplicates are discarded
- unionAll : duplicates are retained
It happened that the tabs of the YT Configuration Editor were not synchronized during edits. It required e.g. to steps incl. an intermediate save if you wanted to add a new data access and a new artifact type. THis has been improved, now you can e.g. map an artifact type to a newly created data access even if the configuration without an intermediate save.
Each selection that happened in the Eclipse Explorer was propagated to YAKINDU Traceability.
As a consequence, the selected resources (i.e. files and folders) and their related artifacts had been visualized in YT.
This worked even for those files and folders which were – according to the YT configuration – not relevant for Traceability.
This has been fixed, selections of irrelevant resources are now ignored by YT.