Currently our workflow for indicating/knowing what app/s need to be deployed for a Jira issue or a Jira release (of multiple issues) is to manually enter/bundle up these from the Jira issue descriptions which we fill out.

What would be amazing though would be if the Octopus Jira integration plugin rendered a smart "section" into the Jira issue, where you could (1) select which apps need to be deployed (from Octopus), and (2) then get a read-only envs+releases matrix like in the octo dashboard so people can see where it's deployed currently.

Furthermore, on the Jira release/deployment page (assuming this can be extended), rendering the superset matrix of all apps needing to be deployed for that release given all tickets in it.

A++, and super complicated for various reasons like ordering, would be being able to create an Octopus "superset release" with a click from that screen, that could then be edited to re-order some things as needed given dependencies, then fired from Octopus (or Jira for that matter).

Finally, depending on Jira workflow support, it'd be cool too if we could tighten this even further and allow workflows to be setup whereby you can't progress an issue into "Ready to deploy" or say give it a release version if the apps to deploy list hasn't been completed.