The current Jira ticket creation automation (as seen in commit 66610fb2) is using the xgen build baron user account. This appears to be due to the automation inheriting the Build Baron credentials currently stored in the environment variables.

Using a personal or existing bot account for general automation creates permission overlaps and makes it difficult to track specific automated actions versus actual Build Baron activities.

Action Required:

Provision a New Service Account: Create a dedicated Jira service account (e.g., jira-automation-bot@mongodb.com) with the minimum necessary permissions to create and edit tickets in the relevant projects.

Generate Credentials: Generate a new Jira API token or OAuth credentials for this service account.

Update Environment Variables: Replace the existing Build Baron credentials in the CI/CD environment with the new service account details:

JIRA_AUTH_ACCESS_TOKEN

JIRA_AUTH_ACCESS_TOKEN_SECRET

JIRA_AUTH_CONSUMER_KEY

JIRA_AUTH_KEY_CERT

Verify: Confirm that the automation successfully creates tickets under the new service account name without affecting existing Build Baron workflows.

Context:
The issue was identified in a Slack discussion where it was noted that the current setup likely just uses whatever is associated with the jira_* environment variables.

Reference Commit:
https://github.com/10gen/mongo/commit/66610fb2bf6a746ac7061fc87f320d7948642ecd