Jira issues from Slack threads at Rippling
Besides the dashboard cron, Rippling engineers trigger Cursor automations that turn Slack threads into Jira issues and Confluence summaries.
- Agent or tool
- Cursor
- Topic
- Productivity
- Reported on
- Blog
- Added
- 2026-10-15
Why it matters
Small, repetitive tasks eat more of the week than anyone likes to admit. Cases like this show an agent taking a chore off someone's plate end to end, not just suggesting what to do. It is one of 196 sightings filed under Productivity on Agent Sightings (number 103 by interest), and one of 30 involving Cursor.
How you could try it
Here is a reusable prompt, written by us in our own words, that captures the task. Paste it into Cursor or any similar agent and adjust the details to your situation.
This Slack thread is a work request. Create a Jira issue with summary, acceptance criteria and links back to the thread. If discussion is long, also draft a Confluence summary page.
The prompt breaks down into 3 steps you can check as the agent works:
- This Slack thread is a work request.
- Create a Jira issue with summary, acceptance criteria and links back to the thread.
- If discussion is long, also draft a Confluence summary page.
Tip: Start small: run it once on a low-stakes example, read what the agent did, and only then let it run on real work.
Source
Read the original first-hand account on Blog: https://cursor.com/blog/automations. Our summary is a paraphrase; details are in the source.