You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We have a project in Github, and I wrote a script that automatically posts a comment on every Jira ticket that is affected by a release that was started on Github, with a Github workflow. It all works great and meets our needs, does what it was designed to do.
The issue is, in order to post the comment, I am using the Jira Python SDK, with my own credentials and an API key that I generated for myself. This means in Jira, all of the comments show up as comments from me, and not from an automated process.
What's the best way to migrate this integration away from depending on my personal user account? Should I work with my IT team to create a new user/email address that would be used to create an account for this integration? Is there another method in the Jira Dev Ops ecosystem that I could use to get this comment to appear on the affected ticket that doesn't make it appear like it's coming from me?
I would say there are two options you can go with.
Work with the IT team on getting a system integration account. This is likely the easiest way since your tooling is already setup to use a user account for the integration.
Another option would be to implement your tool as an app for Jira either a P2 (server/data center) app or a connect/forge app for Jira cloud. For the cloud app the comment would appear as made by the app user. For the server/data center app you would still need a user but this could be easily configured within Jira itself.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.