“New flows have moved from creating user stories to PRD -> stories -> acceptance criteria in a single document in .md file Claude helps with classifying it and linking as well as jira ticket creation. The pipeline then creates the work breakdown tickets automatically.”
“I mean Jira ticking and knowledge base software is free up to 10 users. Although if you want auditing and real support when stuff isn't working consider going for the standard plan.”
“I submitted a report to 365 on the issue and I'm seeing what Jira support says about it now. Not sure they can do much other than escalate to MS if it is indeed just false positives and not a change to how they are sending emails.”
“Jira apis are free to use, and fully featured. What is the 99$ price tag enabling that makes it unique? I understand development needs to be sustainable.”
“I think for starter, you just need to make sure your AI (Claude or ChatGPT) has access to Jira and the prototype. Then, you'll need to make sure to write a skills that make sense for your team so the AI can create tickets in the format that your team is used to.”
“Create a template JIRA format that works best for you and your dev team - spend some time with the tech lead to vet the format e.g., sections can be something like background -> biz need -> ACs -> jobs to be done -> additional info”
“The tool helps you build requirements and other assets links to Figma, storybook, confluence, notion, and M365 and can generate work items and then sync them to Jira or Azure DevOps. The work time sync feature should finish being tested this week.”
“I personally like Jira and supported this. With Jira came more and more PMs, Defect Manager and other imagined titles, as of now we have about 200-250 people working as PMs and similar.”
“I run a similar loop on ERP-like products: Claude Code reads the PRD, proposes the breakdown, drafts the tickets in a fixed shape (context, scope, acceptance criteria), and I edit before anything lands in Jira. The mechanical part is genuinely faster.”
“First I would suggest to move away from Jira as an obsolete platform. Many new CWM tools cover your case better with the **right** MCP tools, but probably you can replicate this with some workarounds in Jira.”
“AI will also guide you through it and you end up with a detailed list of steps that need to happen (including order and dependencies) -> then you just ask it to create tickets for you (using Jira or Linear MCP)”
“Once you are satisfied with the docs you can have AI write the tickets directly into Jira or Linear and assign the tickets to every one. It will write the tickets in a way that they are ready for the developer.”
“Yes I’ve seen very little change over the past 3 years in my role (platform engineering) except mostly JIRA tickets are more unreadable because people just have Claude vomit a novel into it.I mean I use it every day of course, but the velocity of work doesn’t really seem to be budging lol.”
“In Jira settings, I can see the field 'Affects Versions' that I want to be able to add to the report fields. In 'Screens' I've gone into the default screen and added the field and it is there, but it doesn't change the structure of the bug reports. What do I do to actually be able to add it?”
“The first time was like that then I made a write jira ticket skill from that effort. It saved important field id's into the skill so the follow ups went through easily without waste”
“As a software developer I only don't completely hate jira because over the years I've had to use so many worse project management tools. Its still wild how bad it is though.”
“As a QA I love Jira, hate me all you want. But I've got traceability of all encoded bugs and exact steps how to reproduce. Written confirmation of what should be and not.”
“Jira, when used well, rocks. Jira, when you are spending time analyzing why you are “behind schedule” based on fake estimates for unimportant tasks and pivots because creatives are inherently fickle and arbitrary and don’t know to how to commit to anything is a nightmare.”
“"too much time on jira" is really "too much time on coordination overhead" & games just make it visible because the craft is so hands-on. every team i know pays this tax - status updates, ticket grooming, hunting the doc, remembering why a decision was made.”
“Can we make a ticket about how much time we spend on Jira and refine that next sprint for product ship in Q3 to make sure we hit our monthly Jira complaint goals?”
“I hate that the work will sometimes revolve around upper management being able to see shit on JIRA, rather than the work itself, which WILL get in the way of getting work done”