Tracking deployments has limited functionality

[vedrani]

Tracking of GH deployments and transforming them to Jira deployments is limited and it's leaking Jira into Github VSC:

• Parse only Jira key from commit message
  • Leaks Jira app rules into commit message guidelines and forcing change of commit message guidelines
• Doesn't analyse GH Deployment payload field or other GH deployment fields

All that results in stiff and strict solution for tracking deployments.

Instead Jira App for GH should parse Jira keys from:

• PR connected to commit
  • PR title
  • PR body
• GH deployment payload field
  • This would allow engineers to inject Jira keys manually in CI adding flexibility and robustness to it considering we are running GHA in various cases

Simplest solution would be just to add here also deployment.payload

jiraIssueKeyParser(`${deployment.ref}\n${message}\n${allCommitsMessages}\n${deployment.payload}`),

And we would have capability to inject Jira keys from outside in flexible way without requirement to change commit messages to contain Jira key.

[mhanley00]

I second this! Any updates here? In the meantime, any suggestions for alternative intermediary solutions other than putting all issue numbers in the commit? I see in the Jira docs deployments are not expected to work with merge commit PRs but it seems like not that long ago this was a feature, this would really, really help automate our workflow https://github.com/atlassian/github-for-jira/issues/855