Troubleshooting Version swimlanes

If the (Scrum or Kanban) agile board's filter you're using to create your story map contains more than one project, the Version swimlane option is disabled.

Dragging an issue from one version to another in the same project only requires us to change the fixVersions field's value. However, since Versions are project-specific, to move an issue from a version in one project to a version in another project would require us to move the issue to the project of the new version. Due to field configurations being different between projects, this is not something we can do reliably via the REST api.  

When the fixVersion field is not on the screen for the issues it is not accessible by Easy Agile TeamRhythm. Some teams (mostly doing SaaS deployments) don't have a need for a version field, so the versions swimlanes make no sense to them.

To add the Fix Version field:

Click on the Project Settings cog icon in the Project sidebar:

Select the Screens tab on the left of the page:

Select the screen associated with the Create & Edit issue operations:

Add the Fix Version/s field to both the Create & Edit issue operations:

When the fixVersion field is hidden on the field configuration for the project/s it is not accessible by Easy Agile User Story Maps. 

To add the Fix Version field:

Click Project Settings in the Project sidebar:

Select the Fields tab:

Select Edit fields from the Actions menu in the top right:

Show the Fix Version/s field:

Releases/Versions are not supported in Team-Managed (Next-Gen) projects by default. As a result, Version swimlanes are disabled for User Story Maps in all team-managed projects. 

When a user isn't granted the “Create Issue” or “Resolve Issue” permission the versions in your project aren't exposed to User Story Maps. This can be resolved by granting the user the “Create Issue” or “Resolve Issue” permission.