Hello Jira gurus, I am not Jira guru who has been given a task to migrate off legacy SQL systems, which includes Jira Data Center.

The current SQL servers are 2016 and need to go - and everything else supports SQL 2025 except for Atlassian products. I really dont want to build out a SQL 2022 cluster just for Atlassian which will be gone in a few years as the on-prem is EoL/EoS soon.

.

Has anyone placed Jira on a SQL 2025 cluster yet?

I have done it in a pre-production system and I am going to run with it for a few weeks before upgrading production.

Atlassian support isn't really a factor as we work in an environment where we cannot share logs/screens etc and usually have to self-solve most of our issues.

Typically placing SQL in the right compatibility mode has worked for most other products that dont have an internal health alert for version checks.

Thank you in advance!

Hi! I have a Jira space for a project I am working on, and the GitHub repository for it is linked to it. However, when making commits with keys for tasks, it doesn't work, and I think this is because Git commits are made with my GitHub no-reply address rather than my actual email. Is there a way to solve this without setting my commit email to my real email? Thanks!

Hi all, more interested then anything else. For us we do fortnightly releases to monthly. I don't know why we are constantly changing things on our jira. We also do a Sandbox test first then re-do to prod process.

Wanted to see what others are doing?

At first we used to put it in pretty quickly, but found people started wanted configuration on the drop of a hat. Out of nowhere a random person wants 20 fields where they use only 1 of them and it affects other peoples projects.

Or a full automation that they forget even exists. Or because they see it easy for me to change things, they almost use it as a testing ground in prod as opposed to actually thinking through requirements.

Would also love advice if you get users like this, ones that demand change right away, or ones that seem to skirt processes to try to push change in. Or the worse, ones who seem to think I magically work for Atlassian or something because they want some functionality that just does not exist but "leadership person said they REALLLLLLY wanted it" blergh. How you deal with users like this?

Cheers!

The new-business director marks three deals Won in Pipedrive before lunch. By afternoon, delivery has three client kickoffs on the calendar — and only one Jira onboarding epic with a contact block, SOW tier, and assignee. The other two are placeholders created from Slack one-liners.

Monday's internal kickoff for the thinnest ticket surfaces the real problem:

Both answers sit in Pipedrive custom fields and a pre-sale call note. Neither made it into Jira. That is a normal agency Pipedrive Jira onboarding failure: the client relationship is scheduled to start, but the client handoff CRM Jira bridge never ran.

Hello

I have a company-managed Space and already have several tasks created. Now, I have a CSV file that new tasks and also updates for existing tasks. For the existing tasks, it has value in 'Issue Key' column. (For new tasks, the cell/value is empty).

Anyway, I am a Jira Admin and i clicked Settings (not project/space setting) and click External System Import. There, I clicked the bottom 'use old/classic import' and uploaded my CSV file.

After choosing the correct Space, I am stuck at the last page where it asks me to map the columns from the CSV file to the fields in Jira. The problem is I do not see 'Issue Key' or 'Issue Id' which means it's not going to overwrite it.

Does anyone know how i can get by this by any chance? Jira AI is telling me that I probably selected a wrong Space or clicked 'Import a CSV' from the Space but I can confirm that this is really not the case.

Thank you!

Edit: I even created a new file that only has existing tasks (with updated values for few fields) but Jira still wouldn't display 'Issue Key' or 'Issue Id' when selecting the mapping.

I was writing some operation guide for Jira admins, and suddenly discover the "old experience" CSV import has been removed in my personal Jira instance.

In its place is a new CSV import. The UI is different but still similar to the old one.

The difference I found? It doesn't work. I uploaded the CSV file, mapped just two columns as Summary and Description, and imported.

No error message, no import report. Just a message saying the import failed and I should try again or contact support.

Also it does not support Team-managed projects. It simply won't allow you to select those spaces.

Hey all.

I have a automation that creates a specific task every day at the same time. Now I’d like to add a checklist in the description field, when that task is created.

I don’t want to use a custom checkbox field, because then those checkboxes would appear on all tasks. I only want them on that one daily automated task though. Creating an extra issue type just for this is not an option.

When you manually edit a description of a ticket you can just type [] and a checkbox will appear. This does not work with automations though.

Any tips?

The company I work for uses Jira Cloud. The settings have been set up some time ago and need a big refresh. What I am referring to is especially everything you can change under the "Jira admin settings" for "workitems". Not sure if there is a term for this.

However, I'm now preparing new schemes, workflows and how they are used in the individual spaces and plans by using a sandbox duplicate.

Do you have any advice for me on preparing this setup? Is there a nicer way to display the entirety of this setup than the admin settings GUI? Are there any predefined setups or best practices you know of? Can you share any experience? Anything that could help me make the result and the process of migration as good as it can be?

I would appreciate your input.

Hey,

I just started working in a team where they don't do much Agile and are quite lost in terms of priority, dates, capacity, velocity...they do use Jira for tickets (with types and priorities) and Kanban boards. We have projects tasks and incidents.

My opinion is that project tasks can be managed through agile workflow and Jira, and incidents via hybrid workflow (Kanban, SLA and priorities). They are not mature to transition to full Agile yet.

I allready setup a reporting board for tickets, and am working on a Jira Plan for project tickets.

My next steps to help them :

• Set up Jira Plan to estimate capacity / completion / dependencies / dates of project tickets
• Clean up ticket states and assignees
• Get metrics to present to them team (Kanban flux mainly)
• Agree on KPI and DORA metrics with the team
• Use the Jira Plan / Kanban to communicate inside / outside the team

I am interested in your input, as i'm only a developer user of Jira, with PMP/Agile/DevOps experience.

Thanks !

**Hi** r/jira **/** r/atlassian**,**

We are a small startup team of 8 (1 Manager/Dev, 1 Backend/DevOps, 2 Frontend, 1 App Dev, 2 QA, 1 UI/UX) working on a hotel management SaaS product. Our tech stack is Node/Express (Backend), React Native (Mobile Apps), Next.js (Web), and GCP (Infra).

We just migrated from Jira Work Management to a fresh **Jira Software (Team-Managed) Kanban project**. Now, we want to set up solid automated workflows to reduce developer overhead.

Here is what we want to automate, following industry best practices:

1. **GitHub Integration & Auto-Transitions:** * When a developer opens a Pull Request on GitHub, the Jira ticket should automatically move from `Development` to `Code Review`. * When the PR is merged into the staging/develop branch, the ticket should automatically move to `Ready for QA` and be assigned to the QA team. * When the parent ticket is marked `Done`, all open sub-tasks should auto-close.
2. **Component-Based Auto-Assignment:** * We have configured architecture-mapped components (e.g., `Guest App`, `Backend API`, `DevOps`). We want tickets to be automatically assigned to the respective role's default owner as soon as a component is tagged.
3. **Stalled Ticket Alerts:** * A daily automated rule that checks if a ticket has been stuck in `Development` or `Code Review` for more than 3 days with no updates. If so, it should flag the ticket and send an alert to our team's communication channel (Slack).
4. **Tracking Tech-Debt & Security:** * We want to track engineering items (like cleaning logs, updating libraries, deleting unused GCP connectors) using `tech-debt` and `security` labels.

**My questions for the community:**

* Can we achieve all of these rules natively using **Jira’s built-in Automation Engine** in a **Team-Managed project (Free tier)**, or will we hit limits/restrictions? * Are there any gotchas we should watch out for when connecting the official "GitHub for Jira" integration on a free plan? * For the stalled ticket alerts, does Jira natively support Slack webhook notifications in the free automation tier, or do we need integrations? * Any best practices for keeping a team-managed project clean as the team scales from 8 to 15+ devs?

Appreciate any advice, templates, or automation rule blueprints you can share!

Hello!

I'm a software developer and also a Jira admin at the company I work for. I've been creating Forge apps here to address the company's specific workflow, and I'd like to know if there are people doing the same. I completely ignore Rovo and all its AI features because of that. Maybe I'm being ignorant and missing something that could speed things up and organize our lives better, but so far I still vouch for Forge apps. When they're not required, we use Jira's API attached to an AI agent to do the rest.

With the recent boom in AI, I've noticed the process of creating these custom Forge apps has become significantly simpler. While you still need some developer skills to understand and validate what's being generated, the AI agents are doing a pretty impressive job when you provide reasonable input that works within Forge's limitations.

For example: We had a problem in some of our workflows that had rules in the "Restrict Transition" section. When those rules aren't respected, the transition to the new status simply disappears from the options in the work item view. People didn't get used to that, and from time to time someone would ask me "Why can't I close this item? I can't see the status." I had to explain every time, so we created a Forge app that validates the workflow's "Restrict Transition" rules and displays them in a panel to explain what's going on to people.

After that app and the ramp up of AI for creating those apps, we're creating more and more tools that help us on every day tasks without paying add-ons from Marketplace. There are free limits for use of Forge apps (since we're running them using Atlassian's server), but I think they're very reasonable before we start to pay for anything. We even re-forged the way approvals are done, as the native approval mechanism of Jira wasn't enough for our needs.

Anyone else has explored this?

I'm completely new to Jira, so apologies if this is a basic question.

I want to automate stakeholder notifications whenever a P1 or P2 major outage is created. The idea is that Jira would send a notification to a predefined stakeholder distribution list (DL) as soon as a P1/P2 incident is logged.

Is this something that can be done natively in Jira? If yes, what's the best way to achieve it?

If Jira alone can't do this, what alternatives would you recommend? I've heard about Atlassian Forge, Automation for Jira, and external tools like Power Automate, but I'm not sure which is the right approach.

I'd really appreciate any guidance, especially if you've implemented something similar before. Thanks!

I am trying to learn Jira from Youtube tutorial but after I login I can see Spaces not projects like the tutorials are showing.
Am I doing anything wrong? or has something changed?

https://www.atlassian.com/software/jira I am here then I select the site to goto Jira

Sorry for the novice level question but I need help.

I have teams that work 99% of the time in a single project. Occasionally, they need to work on issues from other projects, and I'd like those issues to appear in the main project's backlog so the team can prioritize and plan them alongside everything else.

The problem is that Jira doesn't allow this. As soon as I modify the backlog JQL filter of the main project's board to include issues from other projects, Jira blocks the sprint because the board filter no longer matches the sprint configuration.

What's the recommended approach in this situation? How can I let the team manage cross-project work in a single backlog without breaking the board or sprint configuration?

UPDATE 07.07.2026:

• The projects are team-managed.
• By "the Sprint doesn't match the JQL filter," I mean that the sprint belongs to ProjectX, but I modified the board filter so that the ProjectX backlog also includes issues assigned to PersonA, PersonB, and PersonC. As a result, issues from other projects now appear in the ProjectX backlog.
• By "the sprint is blocked," I mean that I can't create, edit, start, or complete sprints.
• I don't want to add an entire project to the ProjectX backlog. I only want issues from other projects to appear there if they are assigned to PersonA, PersonB, or PersonC.

Hello, nothing changed in our config but we haven't been able to assign or change any "user" type field in our tickets from this morning.

The dropdown has a spinner and ends up displaying "no options"

Does anyone have the same issue? Europe/France

we link specs and runbooks to epics, then the epic moves on. scope changes, tickets get dropped, statuses shift, and the page just stays wrong. found out last month when someone built off a spec that was two scope changes out of date.

review reminder apps don't really help because age isn't the problem. we have 2 year old pages that are fine and pages from last sprint that are already wrong.

does anyone have a process that actually works for this? and if you use one of the expiry/review apps, do people genuinely re-check the content or just click "still valid" and move on?

Hi, can Rolling up time, Sub tasks to Issues to Epics be done? If yes, how and as much clear detail as possible please. Currently, we record time on tasks but it’s not rolling all the way to Epic only to issues.

I recently switched jobs and my new company uses the Jira suite of products. I came from the Connectwise suite. I just missed the conference last month. Short of asking my admins "Can we do X, Can we do Y", Are there any good resources to see their capabilities?

Hello all!

I'm hoping someone maybe has run into this and could give some insight on how to resolve this issue.

The automation I have built out should only create a single instance of this ticket for the triggering issue.

The rule I have built is as follows:

1. Trigger: Runs every 30 minutes. With a JQL search of: "issuetype = Onboarding AND "Start Date" >= -60d AND "Start Date" <= 2d AND status != Closed"
2. Action: Re-fetch Work Item Data
3. Condition: JQL Condition - IF work item matches JQL = "Type" = "New Employee"
4. Condition: JQL Condition - IF work item matches JQL = "Computer Access?" = "Yes"
5. Condition: Related Work Items Condition - Related Work Items = Linked Work Items - All Link Types - Condition: "None match specified JQL" - Matching JQL "summary ~ "Employee Hire - New Computer"
6. Create new task within ONB project with summary of "Employee Hire - New Computer". Link newly created work item to trigger issue.

__________________________________

I've tried the following approaches, but either duplicate tickets are still created or no ticket is generated at all:

1. Changed the Related Work Item Condition

• Changed the condition from "If NONE" to "If SOME" using the same JQL currently configured.
• Result: No ticket is created if any linked ticket already exists, even when it is not the specific ticket I'm trying to prevent from duplicating.

2. Replaced the Related Work Item Condition with a Lookup Work Items action
JQL used:

```issue in linkedIssues("{{issue.key}}") AND summary = "Employee Hire - New Computer"```

2a. Added a Smart Values condition

```{{lookupIssues.size}} = 0```

• Result: No ticket is created.
• Automation log message: "A search during custom value definition found no issues."

I have a feeling that the related work item condition is not recognizing or seeing that there is a linked ticket with this summary but I'm not sure how to ensure that automation does identify that it already exists or does not. Has anyone run into this issue before? If so, I would appreciate any guidance on this!

We're evaluating a few Jira dc alternatives right now and have been sitting through a bunch of vendor demos. Most of the conversations around issue migration sound pretty reasonable. The part I'm struggling to get a straight answer on is scriptrunner.

Our Jira instance has been around for years, so we've accumulated quite a bit of automation. Some of it is clearly business-critical.

A few vendors have said things like "we'll help rebuild the logic" or "it depends on the script," but nobody has really explained what that process actually looks like.

For anyone who has migrated away from Jira dc or cleaned up a large scriptrunner setup:

• Did you try to convert scripts one by one?
• Were you able to migrate most of your ScriptRunner rules? About how long did it take?
• If you've already been through this, was it worth it in the end?

I'm trying to understand where the real effort went. The demos make it sound manageable, but I'm guessing the reality is a bit messier.

Hey Everyone,

I'm reaching out here (bit of desperation) in hopes to get some insight to the current state of the job market relating to Atlassian/Jira admin jobs. I was laid off earlier this year and I have almost a decade of experience in the Atlassian eco-system, with a majority of that doing backend enterprise administration.

I've been having a hell of a time trying to land an offer, even getting interviews has been a struggle. Wanted to post here to see if anyone has landed a role recently or that is currently navigating the market that has any advice or tips? Or is it just a product of all the lay offs?

Appreciate any advice offered, thanks!!