Hey folks! Our company runs multiple ServiceNow instances and we’re looking to set up a smooth integration with Jira Cloud. I’m curious about your experiences.
We’ve got a team handling about 100 requests monthly through a catalog item in ServiceNow. The challenge is getting all the RITM details into Jira stories efficiently. How are you managing this data transfer?
Also, we’re facing some frustration because team members need ServiceNow licenses to work on tickets that end up in Jira anyway. It feels like we’re doubling up on data. Any tips on streamlining this process?
We use AHA! for feature tracking and reporting too. How have you tackled similar setups?
Quick stats:
Requests per year: ~1,200
Current setup: Catalog item + flow to assignment groups
Goal: Seamless data flow from ServiceNow to Jira stories
Having worked on similar integrations, I can offer some practical advice. We found success using Tasktop Integration Hub to connect ServiceNow and Jira Cloud. It handles the data transfer seamlessly, reducing manual work significantly.
For the license issue, we implemented a tiered access system. Most team members use a custom ServiceNow portal with limited functionality, requiring fewer licenses. Only key personnel retain full access.
To streamline the process, we automated the creation of Jira stories based on specific ServiceNow RITM criteria. This approach minimized data duplication and improved efficiency.
Regarding AHA!, we integrated it directly with Jira rather than ServiceNow. This allowed for better feature tracking and reporting without complicating the ServiceNow-Jira setup.
Remember, thorough testing and gradual rollout are crucial for a smooth transition. It took us some time to fine-tune, but the end result was worth the effort.
hey, we faced similar probs. our solution: used Jira’s REST API to push RITM deets directly to Jira. it’s not perfect but way better than manual entry. for licenses, we made a custom portal in ServiceNow for most folks, only leads keep full access. AHA! we connected straight to Jira, skipping ServiceNow. took some tweaking but works great now. good luck!
I’ve been through a similar integration journey, and I can share some insights that might help. We initially struggled with the double data entry issue you mentioned, but we found a solution that worked well for us.
We ended up using the ServiceNow Jira Integration app from the ServiceNow store. It’s not perfect, but it significantly reduced our manual work. We set up bidirectional synchronization between ServiceNow and Jira, which allowed us to create Jira issues automatically when certain conditions were met in ServiceNow.
For the license issue, we implemented a hybrid approach. Only key team members who needed to interact with both systems kept their ServiceNow licenses. For others, we set up a custom portal in ServiceNow that didn’t require a full license but still allowed basic ticket creation and updates.
Regarding AHA!, we integrated it with Jira using their native integration. This way, we maintained a single source of truth in Jira, which then fed into AHA! for higher-level planning and reporting.
One last tip: invest time in mapping fields correctly between systems. It’s tedious but pays off in the long run. Good luck with your integration!