A big chunk of our workflow involves creating and updating Jira tickets, and right now that’s mostly manual. I’m hoping Tines can take over the repetitive parts, like creating a ticket when an alert fires, updating fields as investigation progresses, or closing tickets automatically when resolved. Is this well-supported, and how involved is the setup?
Yes, Jira is one of the most common integrations people build in Tines. The platform has lots of prebuilt Jira templates for standard operations like creating issues, updating fields, or adding comments (just search for “Jira” in the story toolbar to browse them). You configure the connection once, then use it across as many stories as you need.
For the workflow you’re describing (create on alert, update as investigation progresses, close on resolution), that’s a pretty standard pattern. You’d typically have a story that receives an alert via webhook, creates the Jira ticket with the relevant fields populated, and then updates or transitions the ticket as downstream actions complete. The setup isn’t heavy, especially if you’re already comfortable with Jira’s project and issue type structure.
You can find more info in Docs, and the Story Library has full example stories you can import and adapt rather than building from scratch.