Add more unique deployment names

Hi - I was wondering if there was some way to customize the “Deployment” or “Pipeline” fields to show more unique information? Or, if an improvement could be made?

Deployments for our team can mean deploying multiple components separately. A frontend, backend, poller/worker service, etc.

In this screenshot you can see that they currently just show “deploy”. But, this isn’t too useful since I don’t know which is which. Once you click the underlying link it will actually take you to the GitHub action, where you can actually determine which belongs to which. It would be nice to map one of these fields to the name of the deploy instead.

Digging into the code here; I suspect this is where they are mapped. deployment.task I suspect resolves to the value deploy for displayName. But, I’m not too sure what to change in my github action, since it doesn’t seem we specify that anywhere.

[benoittgt]

Hello

Ok after diging a little bit. I think the current implementation is good but it needs some documentation and maybe the field “deployment” should print another info. Few ideas:

• the commit (similar to https://github.com/atlassian/github-for-jira/pull/1732)
• the description of “deployment”
• Even better the description of the “deployment status”.

For all those ideas “Deployment” should not have a link, but env should be mapped to environment_url (https://docs.github.com/en/rest/deployments/statuses#create-a-deployment-status)

With the existing implementation, to change the content of deploy and pipeline simply specify in Github Action the name of the task.

I do not use Github Action, but I was able to make this with the proper API calls on Github API.

[dt-atkinson]

Perhaps the deployment payload (on creation) can be used for these extra details if we have unique keys that can be looked up?

For example your deployment could easily have a pipeline and deployment key string added there, possibly nested under a jira info key?