“Curious though, was hooking Jira's audit log into it actually easy, or did it take real setup (the 180 day cap, event ID dedup, that kind of thing)? And separately, do you know anyone at a similar stage as you but without a SIEM yet?”
“Everyone's got the integrations now. Slack, CRM, Jira, docs. I've got that stacked across every business I'm in, and the model still shows up to each question with no idea how any of it actually works and starts”
“My bull case for Linear was an eng at Uber, Airbnb + a designer at Coinbase all got fed up with how much time they wasted on JIRA, Phabricator & others for tickets / organizing work.”
“Every PM I've worked with ends up keeping their own Confluence page or spreadsheet for things like "what we owe this client by the 14th" or "what we're showing in Thursday's exec review." Tickets get pasted in, statuses get hand-updated before each meeting, and it's stale by the following week.”
“Honestly the worst part is when someone updates a ticket in Jira but forgets to ping the Slack thread, so half the team keeps working off old info until someone randomly checks. That and digging through three different tools just to figure out if a PR actually passed CI or not.”
“Was wondering if they ever got Jira and Confluence to have bidirectional editability. Eg., Jira ticket content that linked in confluence gets edited in Confluence and changes are reflected in both Jira and Confluence.”
“the constant mental gymnastics of keeping jira ticket statuses in sync with what's actually happening in github PRs is maddening. someone merges a PR but forgets to move the ticket, or they move the ticket but the branch name doesn't match the convention so nothing links up.”
“Rovo is better than any other AI in searching in Jira or Confluence. The most powerful is the context that Atlassian called Teamwork Graph. When you connect third party tools like Gdrive or HubSpot, they all can be searchable with Rovo.”
“It’s something Atlassian will rollout soonish: https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/Deploy-configuration-changes-from-Sandbox-now-in-Open-Beta/ba-p/3257493 only on premium and enterprise plans though.”
“Is there a built-in way to export/import project configs, or do most of you just recreate everything manually on the production side? Would really appreciate any tips, tools, or gotchas to watch out for from people who’ve done this before.”
“When a req is open it’s a top priority of whoever is in charge.You can be PM-nonexistent or PM-heavy with lots of meetings and JIRA. Maybe you can accomplish all 3 above in both worlds.”
“It is simple I’ll leave it do Claude or Jira’s coding agent to do it in a remote coding env. It it’s complex I’ll create a local worktree, point Rovo, or Claude or codex as the ticket and then do a back and forth pairing session with the agent.”
“I forgot to add, we got shown these new Jira coding agents in a roadshow event, you can assign work to an agent and it will spin up a code space, very cool stuff.”
“Not sure what there is to orchestrate, Claude Code at least the desktop app allows you to run multiple sessions, just send each agent a Jira ticket and off it goes.”
“add different columns to your Jira board to support all phases of the workflow: To Do, In Progress, Blocked, QA Ready, QA Complete, Ready for client, Client Feedback Received, Completed - you can track the date ready for client and the date completed as two separate dates if you want to report on that field.”
“We typically use Jira user stories to track different work items. In a specific project that I’m working on, the data analyst from my team creates Power BI reports and dashboards.”
“I can also see my open PRs including when PRs get approved; as well as some Jira context.I usually limit # of concurrent tmux windows 15 (per Kanban limit of Work In Progress concept) but I've been known to up that to 30 when on-call.”
“I hear a lot about the future of software engineering work being an engineer sitting with tons of sessions open and multitasking on many jira tickets all at once.”
“We do use Rovo alot, but mostly as backend agents doing some automated work - like incoming ticket triage, automatic replies if they find match in the knowledge base, some fidelity testing in the incoming tickets, proposing similar tickets and possible connected ticket across the Jira.”
“Use a Jira filter to identify tickets with no owner, no priority, or no update in 90–180 days, then review those in short batches with the PM and a senior engineer. Anything without a clear user impact, owner, or realistic time horizon gets closed.”
“Approvers in particular kept missing approvals sitting in an instance they don't check daily which means blocked requests, annoyed requesters, and people pinging approvers directly instead of trusting the queue.”