“Jira can work for smaller programs if the workflow is well designed. the important pieces are making sure approvals, reviewers, evidence, timestamps and exceptions are all captured clearly for audits”
“Jira giving you flexibility and you complain. Team system field is here to stay so update your Team custom field name to something else or build out teams in Jira and remove the team customer field name field.”
“Everything in Jira boils down to the ID, this is a pain we have also felt. Jira doesn't care what you name the thing, and before I was an admin the custom field ID was my biggest pain point.”
“On one hand, Jira allows you to name custom fields with the same name. On the other, Jira doesn't show you any other details when you have to pick a field.”
“jira deployments diffing shas between deploy events is exactly why you get unrelated tickets bundled in.. that approach assumes linear history between two points, which short-lived branches merging to main constantly breaks.”
“The natural next step is the REST API, which can create work items in bulk (up to 50 per request). A small script can read each system's export, create the items and write the row counts to the parent for you.”
“Jira can work well for User Access Reviews if you mainly need workflow, approvals, and an audit trail. The challenge is keeping access data updated and automating remediation.”
“Jira can be capable of managing the process as it can allow you to enforce gates at each step in the progress - i.e. step 1, request list. Step 2 someone confirms c&a (that's likely not the list make) and so on.”
“Jira Deployments attaches issues by diffing the commit range between two deployment events, so with short-lived branches squashed into main the range stops matching one unit of work — you get the same ticket on five deploys and unrelated tickets riding along. It is a model mismatch, not a bug.”
“We are feeding ticket into our jira board, it pulls them from there and just work on them until eveything is done. We trust it enough that we've enabled auto approve mode so all PRs no_human ships - are approved and merged automatically (this feature hasn't been released yet).”
“Can't you have a dedicated status or field in Jira that match your deployment stages? In my team, we have a status "prod", can be set manually or via our system that deploys to prod.”
“Ask for proposed edits before syncing to Jira. Otherwise, a small product change can leave you with several detailed tickets describing different versions of the feature.”
“jira can work but you'll be fighting it the whole way for row-level approvals on thousands of records, the data model just isn't built for that and you'll end up with a mess of custom fields and automation rules that break when someone sneezes”
“JIRA <-> GitLab/GitHub integration and just refer ticket in branch name or commit message and it immediately goes against that ticket. Other PMO tools may have similar integrations.”
“We have a rule that every branch must have a Jira ticket number attached, the ticket then moves on the board, the PM tracks the ticket, and when it hits a certain swimlane you know where that ticket is in the sprint and what environment(labels too). The PM manages the whole ticket timeline because they hear about blockers/issues in stand up each day.”
“we turned on jira deployments a while back thinking that solves it, but the panel shows the same ticket as deployed like 4-5 separate times, and tickets from totally unrelated work show up in deploys they have nothing to do with. i *think* its diffing shas between deploy events and just attaching everything in between?”
“I spend 75% of my week in alignment meetings, Jira updates, and change-request approvals. I haven't written code that genuinely challenged me in two years."”
“Like “JIRA to product” nonsense. Is like we can hand wave the details that matter and somehow the end product would still be what we want.Not even talking about the degenerative codebase you mention, which is also an issue I am seeing after some time in any project.”
“When you see the questions to jira tasks you worry about if they don’t forget to eat or go to the toilet randomly. Oh yeah, most are classified as seniors.”
“I'm in the security governance space, and curious if anyone uses a well-automtated, streamlined Jira workflow to manage user access reviews? I'm in a heavily regulated + SOX environment, so completeness/accuracy validations and transparency in reviewers (i.e.”
“pricing is totally fine i think. reason: JIRA is used in commercial company contexts. People who work wit jira usally move much more money than $2,99 ;)”
“Tools like Jira are bureaucracy-management tools, not Agile tools. You don't need a backlog at all to get work done—a handful of index cards or stickies work just fine, and more than a couple of weeks' work in that pile is too much.”
“GitHub. Azure DevOps. Jira. Confluence. Your engineers run on tools that weren't built with recovery in mind, and AI coding agents are now pushing more code through them than your team ever did. Volume is up, complexity is up, and so are the risks.”
“Given the app talks straight to Jira's API and your server only handles the sign-in, a lower lifetime or a version-locked licence would land better with this crowd than the monthly.”