I release, milestone 1 (IM1 1.1.1801)

New setup wizard

We added a wizard providing guidance on how to set up an empty workspace. It helps unexperienced users to create or import projects or YAKINDU Traceability configurations.

New setup wizard

Polarion adapter supports attributes

The Polarion adapter now supports the retrieval of work items attributes. Here’s an example taken from the corresponding documentation section:

You can map attributes, too. Example:

include objects if(
	valueOf(type)=="userstory"
)
map{
	attribute to valueOf(author)
	^severity to valueOf(severity)
}
name valueOf(id)

This example expands the previous example. Here we are mapping two attributes to the values of a Polarion work item.

New link storage for text files

The text file adapter now supports storing link information in text files invasively.

The following image illustrates this:

New link storage for text files

In the YT configuration belonging to this screenshot, requirements in the text file are recognized based on the pattern „REQ” followed by digits, and links are recognized based on the pattern „@LinkedDetailedDesign:” followed by the path to the linked artifact.

Links can be created using the YT Editor or by a simple drag-and-drop operation.

Usability improvement for validations

If the user is notified that the YT validation has found some issues, YT now offers a link to immediately navigate to the YT Issues view.

Usability improvement for validations

Constraint that only one PTC Integrity data access can be active is now explicit

YT now validates that only one PTC Integrity data access is active.

Constraint that only one PTC Integrity data access can be active is now explicit

Better notification if server port in use

YT now explicitly notifies the user if it cannot offer remote procedure calls due to the configured port being already in use. This may occur if, e.g., more than one YT instances are running on the same machine.

Better notification if server port in use

Better consistency in YT configuration editor

In some situations, changes to the configuration that had been specified on one tab were not propagated unless the configuration was saved. If a user, e.g., created a new data access, this new data access was not available for the mapping definition of artifact types unless the configuration file was saved or the editor was refreshed. This has been fixed.

Fixed a bug in the YT editor when replacing artifacts

If a user wants to replace the very same artifact in all links from/to that artifact, e.g., because the original artifact has been deleted and a new one has been created instead, the Artifact search dialog now displays artifacts of the correct type only.

Better consistency in YT configuration editor

Documentation overhauled

The documentation sections on several topics have been overhauled and extended considerably: