-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking deployments has limited functionality #2421
Comments
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 #855 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tracking of GH deployments and transforming them to Jira deployments is limited and it's leaking Jira into Github VSC:
payload
field or other GH deployment fieldsAll that results in stiff and strict solution for tracking deployments.
Instead Jira App for GH should parse Jira keys from:
payload
fieldSimplest solution would be just to add here also
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.
The text was updated successfully, but these errors were encountered: