Is there a way for TeamCity to work with JIRA similarly to how Bamboo does? I haven’t come across any official JetBrains documentation addressing integration with issue-tracker systems. Moreover, I’ve heard rumors that TeamCity might introduce its own tracking tool called Charisma. Can anyone confirm if this is true or explain if such integration is supported in any form?
hey, i’ve ran into this before. the integration isn’t built-in like bamboo, but you can use jira’s rest api with teamcity to get it working. as for the ‘charisma’, i haven’t seen any reliable info on that, so might just be hearsay.
Based on my own experience working on a similar integration, I managed to configure TeamCity to interact with JIRA by leveraging JIRA’s REST API. Though it does require additional work compared with an out-of-the-box solution like Bamboo’s integration, the setup is both feasible and reliable when carefully tailored to your workflow. Custom scripts and webhooks can bridge the two systems effectively. I have not encountered any valid references regarding a tracking tool called Charisma, and it appears this might just be industry chatter rather than a confirmed feature.
I have experimented with integrating TeamCity and JIRA on a project and found that, while there is no native support similar to Bamboo’s integrated solution, it is still possible through custom implementations. In my case, I used JIRA’s REST API along with some custom scripts triggered by TeamCity build events. This approach, albeit a bit more hands-on, allowed for efficient status updates and issue tracking. Regarding Charisma, I have not seen any official release or confirmation from JetBrains, and it appears to be more speculative than a developed feature.
hey, i got teamcity and jira working together by using a custom webhook with jira’s rest api. took a bit of tweaking but it runs smooth. no sign of any jetbrains ‘charisma’, so seems just a hype, imho.
I have worked on integrating TeamCity with JIRA for an internal project where I needed automatic issue updates post-build. My approach involved setting up custom scripts that interfaced directly with JIRA’s REST API, ensuring that build results directly impacted issue statuses. This required careful handling of authentication and response parsing, but ultimately provided seamless communication between both tools. I have not encountered any official announcements for a tracking tool like Charisma, so it appears to remain an unconfirmed rumor at this point.