Undefined Repository Version Type

When connecting a software item to a repository, the operation succeeded, but the Repository version type appears as Undefined.

Cause

If the Repostiory version refers to an identifier that does not exist yet, the app does not resolve the version, which is considered undefined by the system until the identifier does exist.

Solution

When the tag or branch that matches the repository version provided is created, the version resolves automatically.

Cause

The system is unable to determine whether the repository version is a branch name or a version tag. This can happen when an object exists on a branch and also has a version tagged with the same name. This is possible on GIT systems, and may be possible with other SCM services supported through custom connectors.

These is no solution for this. If the system is unable to resolve the tag to a specific branch or tag, it will continue to display that the repository version is undefined.