More configurable Jira integration for metadata deployments
The Jira integration for metadata deployments would be much more useful with additional configuration options. Here are a few suggestions.
Comment controls: Allow comments to be turned off entirely so the integration only adds the attachment and updates the status. Alternatively, allow comments to be limited to production deployments only.
Jira tickets on draft deployments: Allow draft deployments to be saved with their linked Jira ticket. When multiple drafts are combined into a package, the linked tickets should carry through to that package automatically.
Default project and automatic ticket matching: Allow a default Jira project to be set. It would also be helpful if Gearset could find the Jira ticket from the deployment’s friendly name, as many teams (including ours) name deployments after the ticket number.
Status updates by target org: Allow status changes to be configured based on the target org. For example, deploying to a UAT org would automatically move the ticket to an “In UAT” status.
These changes would reduce manual steps and keep Jira tickets accurate without extra noise.