Sending deployment events to Jira on merge to master not working

Summary

When merging to master my CI pipeline runs a production deployment. This production event does not successfully reach Jira (although staging deployments do).

Steps to reproduce

1. Install Jira markeplace app in jira and setup following this guide https://www.youtube.com/watch?v=P7EDRaMRWPE
2. Set up gitlab CI/CD pipeline

# This file is a template, and might need editing before it works on your project.
# Official framework image. Look for the different tagged releases at:
# https://hub.docker.com/r/library/node/tags/
image: node:latest

# This folder is cached between builds
# http://docs.gitlab.com/ee/ci/yaml/README.html#cache
cache:
  paths:
    - node_modules/

stages:
  - test
  - build
  - deploy

build:
  stage: build
  script:
    - npm install
    - npm run build
    
deploy_staging:
  stage: deploy
  script:
    - echo "Deploy to staging server yay"
  environment:
    name: staging
    url: https://staging.example.com

deploy_production:
  stage: deploy
  script:
    - echo "Deploy to prod server"
  environment:
    name: production
    url: https://prod.example.com
  only:
    - master

3. Create commit and merge request, noting that deployment event is successfully sent to jira for this "dummy" "staging" branch deployment. Yay!
4. Merge PR and note that production deployment step ran
5. Check Jira issue for Production deployment event and be disappointed that it doesnt appear :(

Example Project

https://gitlab.com/mynamspace/mustard-modifier

What is the current bug behavior?

My production deployment step

deploy_production:
  stage: deploy
  script:
    - echo "Deploy to prod server"
  environment:
    name: production
    url: https://prod.example.com
  only:
    - master

does not successfully send a production deployment event to jira to be associated with my issue key.

What is the expected correct behavior?

I expect that a production deployment event would be sent to jira and would be visible on the dev info dialog in jira

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Results of GitLab application Check

Possible fixes

Obviously this could be an issue with my pipeline. Apologies if it is.