Problem Definition

In the Deployments UI, Environments often have associated links that point to the latest Release that was successfully deployed to the environment. This includes the "All Deployment Projects", Specific Deployment Project, and "Environment" status pages. (Check "Projects Overview" attachment for an example)

On the Release status page (for a particular release), there is a list of Environments in the Deployment project. If the release was not deployed to an environment, this page shows "Never Deployed" next to that Environment, followed by a "Now at <Release-name>."

The "Now at" message on this page then references the latest Release that was attempted to be deployed to the environment. This is regardless if the release was successfully deployed or not. Please see attachment "Now at message."

This behaviour occurs when the deployment to the environment fails and has the status of "not-built." In the case of the screenshot examples, the release that failed to deploy was "release-8."

Suggested Solution

Remove UI inconsistency by changing the "Now at" release to point to the last successful release that was deployed to said environment.

Why this is important

This can cause confusion on which release was actually deployed to the environment, when viewing another release status.