Olha Yevdokymova_SaaSJet Atlassian Partner

Offboarding is now one of the most challenging workflows in business operations. In 2026, global trackers reported over 232,000 job cuts from more than 500 layoff events, averaging about 770 per day. More than a third of these exits are now due to automation, organizational changes, and shifting budgets from staff to…

Two weeks into piloting Atlassian Rovo, an engineering director asks what should be a routine question: "Who needs to approve a production hotfix on the payment gateway after 6 PM?" Rovo answers in two seconds with unwavering certainty: "Approval must come from Dave Miller, with an architecture review filed under project…

Intake Forms in Jira and Jira Service Management for Healthcare Operations Most healthcare organizations don't use Jira as a clinical system. Instead, Jira is great for handling the operational work that supports care: clinical IT support, application incidents, access requests, EHR change control, quality and CAPA…

Most Jira instances suffer from the same invisible disease: intake decay. It starts innocently. A team needs to collect three new pieces of context for a bug or a campaign. Someone with admin rights adds three custom fields. Six months later, your instance has 450 custom fields, eight variations of "Product Area", six…

When a support conversation in Jira Service Management (JSM) turns into "I wish the system could do X," you are no longer handling an incident - you are holding valuable product feedback. Licensing thousands of JSM portal-only customers in Jira Product Discovery (JPD) isn't practical or cost-effective, but you can build a…

If you’ve ever wished your customers or internal teams could submit Jira tickets without accessing Jira itself — you’re not alone. Many organizations struggle to create a smooth, branded way for users to raise requests directly from their website. Jira Service Management offers a portal, but what if you’re using Jira…

Not every work item in Jira moves neatly from To Do to Done in a few hours. Some issues develop over time: new evidence comes to light, witness statements need collecting, compliance decisions must be documented, and corrective actions spill over into completely different project boards. Employee grievances, safety…

Most intake forms are built for a single, fleeting moment. Someone fills out the fields, hits submit, the data lands inside a Jira work item, and the form locks down forever. What got captured right then is a snapshot—one person's answer, frozen in time at 9:00 AM on a Monday. That setup works brilliantly right up until…

Your organization may already manage laptops, applications, cloud environments, vendors, and office locations inside Jira Assets. However, the operational teams executing the work - engineering, IT, security, and facilities - frequently work inside Jira Software projects. When request forms rely on open free-text fields,…

 At first glance, today’s employee help centres seem almost magical.HR teams upload their policies and onboarding guides to Confluence. Employees then log into the Jira Service Management (JSM) Help Center, ask a quick question to an AI assistant like Atlassian Rovo, get an instant answer, and move on without needing to…

If your team collects numeric data through Jira—whether for equipment orders, travel requests, marketing budgets, or IT risk scoring—you’ve likely faced the post-submission math gap. Requesters fill out quantities or hours, but the total cost or risk score remains blank. Your receiving team then has to open a spreadsheet,…

Did you know that more than 40% of business trips are delayed or canceled—not because flights are sold out, but due to simple process confusion? During peak travel seasons, managers face chaos as requests pile up. The core challenge isn't just capturing the initial request—it's coordinating a multi-team lifecycle across…

Many feedback systems do not work well because they simply count solutions instead of capturing the real problems. For example, when a customer asks for a "bulk export button," they are pointing out a symptom, not the root workflow issue. If you only track upvotes or feature requests, your product team may end up building…

Before any numbers make it to ONESOURCE, Bloomberg Tax, or an external auditor, your team faces a messy process of gathering data. A local controller might email a huge file of jurisdiction data. The finance team sends a trial balance. Procurement urgently requests a W-9 so a vendor payment can go through. The actual…

If you're part of the Jira Cloud admin community, you've probably heard that field configuration schemes are being retired. Beginning in June 2026, the new Jira Field Schemes model starts rolling out, offering a more modular setup. Most migrations will happen on their own — but "automatic" is exactly the catch: Atlassian…

Tired of rebuilding the same form? If you’ve ever had to recreate the same “Vacation Request” or “New Hire Checklist” form in three different Jira projects, you know the pain. It’s like playing copy-paste on repeat — HR wants it, Finance wants it, IT wants it. Before you know it, you’ve built five versions of the same…

A lot of teams set up a Rovo agent with Jira and hope for quick results. While it sometimes works, the agent often gets confused, sends tickets to the wrong place, or asks for information that should already be in the ticket.This isn’t actually Rovo’s fault. The real problem is with the data.The agent didn’t fail—it just…

Jira has traditionally been a platform for recording work, but this is changing quickly. Now, with Rovo agents, the Teamwork Graph, and MCP integrations, Jira is becoming more than a place to record work. It is becoming a connected work system where structured Jira data can be searched, interpreted, summarized, and acted…

Here I am going to describe New Jira Automated actions to add the right form on the right workflow moment that support Jira Software or JSM projects. Jira Automation handles the mechanical parts well — assigning tickets, updating fields, sending notifications, moving statuses. For a lot of workflows, that's enough. But…

I'm starting a series called Tips & Tricks with Smart Forms for Jira — short posts about configuration patterns that aren't obvious from the docs but save a lot of pain once you know them. First one: approval routing. Specifically this question, which I see constantly: "How do I automatically assign the right approver…

Most Atlassian articles assume everyone working with Jira is also working inside Jira. But that's rarely true at larger organizations. Your legal team is in SharePoint. Finance runs approvals through Power Automate. Half the company communicates exclusively in Teams. They don't have Jira licenses, they don't want Jira…

Change requests are supposed to make managing change easier. But often, they show up as a vague Slack message, an incomplete ticket, or an email with no rollback plan. Reviewers then spend the start of the week tracking down missing details. A well-designed Jira change request form solves this problem from the start. It…

Jira Issue Collector was supposed to be the tiny bridge between “someone has feedback” and “the team can act on it.” For a while, it did the job. A simple form on a website. A quick submission. A new Jira work item. But modern teams rarely need “just a form” anymore. They need the form to ask different questions depending…

You can polish a workflow until it shines, but if your team is drowning, the board will always be a graveyard. Here's a fun experience. You finally sit down to work. You open Jira. And immediately your brain goes: oh right, you never replied to that client, also the sprint board is a disaster, also remember that thing from…

"We have hundreds (or thousands) of custom fields and nobody knows which ones are safe to delete." - If you've ever said this, you know the cost of field sprawl — and that the fix usually isn't another field. It's knowing when to capture data in a Jira form instead. Designing your Jira intake around dynamic forms, not…

Modern teams don’t live in a single tool anymore. Your developers are in Jira, marketing coordinates in Asana, sales runs in Slack, and operations tracks tasks in ClickUp. The pain starts the moment someone outside your Jira projects needs work from your team.​ You’ve seen this pattern: * A Slack DM: “Hey, can you create a…

What's different, and what it means if you're thinking about moving to Cloud ProForma has been the go-to form solution for Jira Service Management teams on Data Center for years. It's well-integrated, well-documented, and many teams have built real workflows on top of it. So when organizations start thinking about a move…

I'd like the form to be open with the Jira issue details already populated in it. That's it. That's the entire request. And yet it turns out to be rather complicated.Here's the scenario that we all come up against. A work item is created automatically (from an intake form, an API call, an automation rule running in the…

Anywhere Jira relies on dates — due dates, requested dates, planned start/end times — those values influence how work is scheduled, prioritized, automated, and measured. At a system level, dates and times are used to: * Start, pause, or breach SLAs * Trigger automation rules and notifications * Drive capacity planning and…