r/jira

I've been using jira for 17 years.

I was potentially one of their biggest fan boys back in the days.

Wow things have changed. by jog is not multiple levels harder than it use to be just because of how terrible the UX has become:

1. Who needs to print tickets for away from screen planning days - feature removed as only 20/10% of users use it (hello project coordinators and scrum masters)
2. time line view drag tickets between epics and with an epic based on priority. - nah best we can do is if we don't understand where you dragged that ticket is to orphen it and let you go find it breaking you work flow on planning crunch days.
3. there are many other minor annoyances being rolled out but these are literally adding hours to my work load at crunch times when you expect the tool just to fricken work.

JIRA: your experience use to be awesome. Now I'm siding with my devs, why the actual?

For those still on Data Center, what does your current plan look like? Are you planning around the March 2028 last-renewal date or the March 2029 end of life?

Would love anyone's real-world view on the plans, the risks, especially the obstacles.

Hi all,

I'm an integration consultant with 12+ years of data migration and integration work, and I'm considering building a small Forge app for Jira Cloud. Before I write any code, I want to check it solves a real problem.

The idea: after a Data Center to Cloud migration, you give the app an export from the source site. It checks every migrated issue against it (comments, attachments, worklogs, links and field values) and gives you a list of exactly what's missing or different, with a link to each affected issue. It would run entirely on Atlassian, so no data leaves your site.

Three questions for anyone who has run or supported a migration:
How do you validate a migration today, beyond comparing totals?
Have you found missing or changed data after go-live, and how did you spot it?
Would you use a tool like this, and what would it need to do for you to trust it?

I've seen MIG-1071 asks for post-migration checks in the migration assistant itself, so I'd also love to hear about any workarounds you use.

Thanks,
Mannie

The standard GitHub-Jira integration works fine for basic setups, but it completely breaks down for us because our Jira projects have required custom fields that are dynamic per team.

When we try to auto-generate a ticket from a new PR, it either fails Jira's validation or creates tracking garbage because the dynamic data is missing.

I'm considering building a lightweight GitHub App to fix this. The idea: teams drop a jira-mapping.yml in their repo to define exactly how PR metadata (branch name, labels, regex from the description) maps to specific Jira custom field IDs.

Before I spend my weekends building this:

How are you solving this today? (Custom in-house webhooks?)

Would a plug-and-play GitHub App actually be useful for your CI/CD pipeline, or is this too niche?