chore(documentation): add jira release note to contributing file

CONTRIBUTING.md

@@ -81,5 +81,6 @@ https://code.visualstudio.com/api/working-with-extensions/continuous-integration
 1. Now let's download the built `.vsix` artifact in the new [GitHub release draft](https://github.com/mongodb-js/vscode/releases) and ensure it works smoothly. https://code.visualstudio.com/docs/editor/extension-marketplace#_install-from-a-vsix Manually test the new version using the testing matrix found here: https://docs.google.com/spreadsheets/d/1014WyX-WPMfZTj6qVyYDA1JowGCFNCOQGgEhIA0O0bs/edit#gid=0 Duplicate the testing template page and rename it the new release. Not every test needs to be performed before we release, however, the critical paths should be tested.
 1. Update the [release notes](https://github.com/mongodb-js/vscode/releases) in GitHub, documenting user facing changes. Once you’re happy with the changes you can publish the release.
 1. When the release is published, the GitHub action https://github.com/mongodb-js/vscode/blob/main/.github/workflows/publish-release.yaml is automatically run, which downloads the release artifact and then publishes it to the VSCode marketplace.
+1. Mark the **release as complete** in [the jira project's releases](https://jira.mongodb.org/projects/VSCODE?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=released-unreleased). Ensure the commits in the github release correspond to the jira release, typically this will involve renaming the `vNext` release as the recently released version, and creating a new `vNext` release.
 1. Nice! ✨ Now you can verify it all completed by visiting https://marketplace.visualstudio.com/items?itemName=mongodb.mongodb-vscode and seeing the new version is up. You also try installing it in VSCode :) ✨
-1. Lastly, don't forget to post in slack, let all your friends know, and close the release ticket in jira if there is one.
+1. Lastly, don't forget to post in slack, let all your friends know, and **close the release ticket in jira**.