Petru Simion [Simitech Ltd.] Atlassian Partner

Atlassian's recent decision to make Assets available directly in Jira Cloud, beyond Jira Service Management, opens up significant new possibilities for organizations using Jira. For many Jira users, Assets may still be associated primarily with IT equipment, configuration management, or service management. However, Assets…

As a Jira administrator, have you ever needed to investigate a configuration change and answer questions such as: Who made a particular change, and when? What was the previous value, and what was it changed to? Which configuration objects have been modified? How frequently are administrative changes occurring? How can I…

Many Jira admins only discover configuration sprawl when something breaks—or when a platform limit appears. With Atlassian introducing a 700-field limit per field configuration in Jira Cloud, many large instances are suddenly much closer to that limit than expected. Over time, most Jira instances accumulate hundreds of…

Migrating Jira from Data Center to Cloud is a significant undertaking. Projects, issues, workflows, users, permissions, and configurations all need to be transferred successfully. But there is one important question that deserves particular attention: How do you verify that the complete history of your issues was preserved…

Moving Jira from Data Center to Cloud is not only a data migration. For long-running Jira environments, one of the most important questions should come before the migration itself: How much of the existing Jira configuration do we actually need to take with us? Years of Jira administration can leave behind custom fields,…

When evaluating a Jira Cloud Marketplace app, seeing that it is Built with Atlassian Forge can be reassuring. Forge provides an Atlassian-managed platform for building and running Jira Cloud applications, and for many organizations it can simplify some of the infrastructure and security questions traditionally associated…

Moving Jira from Data Center to Cloud is a major undertaking. Teams can spend months analyzing projects, cleaning up configurations, testing migrations, and planning the transition. But there is another part of the migration that can become a problem if it is considered too late: Marketplace application compatibility. And…

One of the questions I've encountered repeatedly when working with Jira Assets is surprisingly simple yet incredibly difficult to answer natively: "What did our Assets actually look like before this happened?" The "event" could be almost anything: * A major Cloud migration or schema cleanup exercise * An external…

One thing I've noticed over years of working with Jira is that most questions are easy to answer when you're looking at the current state of an issue. The challenge starts when someone asks about the past—not just for a single issue, but across dozens, hundreds, or even thousands of issues. That's usually when teams end up…

Time in Status sounds simple. You look at an issue, you see how long it stayed in each status, you aggregate that, done. That’s how it looks when you test it on a small project. Then you run it on something big. And suddenly: it takes forever results look off or inconsistent or it just doesn’t finish What changed isn’t the…

One thing that sounds simple in Jira, but really isn’t once data grows, is history. Questions like: when exactly did this changehow long did it stay in a statuswhat was the value before look straightforward. Until you try to answer them across a large project. On a small dataset, you don’t notice anything. You run…

If you’ve only worked with smaller Jira projects, reporting feels… fine. You run a query, maybe export something, maybe build a report, and that’s it. The problems only show up later, and not all at once. At some point the data grows and things start getting weird. Queries that used to take seconds now take minutes.…

Hi everyone 👋 Over the past months, we’ve received a lot of feedback from teams who use Jira not just for tracking work, but for understanding how work actually flows. Based on that, we’ve recently introduced two improvements in Time in Status Reporter for Jira , one of the apps released by our team, that focus on deeper…

A recurring challenge when reporting on cycle time and lead time in Jira is that these concepts are semantic, while workflows are structural. In real Jira environments: * Stories, bugs, and tasks often follow different workflows * Some issue types include rework states such as Reopened * Others skip entire stages or use…

Our company has developed several Jira apps over time, each focused on a different aspect of understanding how issues evolve. Based on how these apps are commonly used together, we now offer them as a single bundle: Issue Insights for Jira. The bundle brings together a complementary set of tools that, when used together,…

Searching Jira comments across many issues is harder than it looks. Native search and JQL can handle some scenarios, but combining comment text, author, dates, and issue fields usually requires complex queries that are difficult to build and maintain. There is a more practical approach: load the relevant issues using…

Over the past months, Issue History Reporter for Jira has evolved based on feedback and requests from the Atlassian Community. The focus has been on giving users more control over how work items are selected and more precision in historical analysis. This article highlights the most important additions. 🔍 More flexible…

In today's fast-paced business environment, teams need quick and easy access to relevant data to make informed decisions. The way we approach data analysis is changing, thanks to advances in Artificial Intelligence (AI). With AI-powered analytics, we can now feed raw data into AI tools and ask verbal questions to get…

In Jira Service Management, Assets are often treated as “just another field” attached to an issue.That mental model is convenient — but fundamentally wrong. Assets are persistent objects.Issues are temporary workflows. And confusing the two is the reason many teams struggle with visibility, accountability, and traceability…

A common challenge when analyzing work in Jira is answering a simple but often unsupported question: “What did this issue look like at a specific point in time?” Jira provides detailed change history, but it does not offer a native way to view the complete state of an issue — across all fields — as it existed on a chosen…

Over the past year, Time in Status Dashboard for Jira has grown far beyond its original purpose. What started as a simple way to measure how long issues spent in each workflow status has steadily evolved based on feedback from teams using it day-to-day. That evolution led to a natural question: Is this still “just” a…

As a Jira administrator, I was once asked a deceptively simple question by management: “Where is this field used?” The goal was reasonable: They wanted to analyze the instance, optimize performance, reduce confusion, and clean up technical debt that had accumulated over years. What I quickly realized was that Jira makes…

When I started building work item (issue) history analytics apps for Jira Cloud, one design decision surprised some users early on: searches were intentionally scoped by project. At first glance, this can feel restrictive. Jira is flexible. JQL is powerful. Why not allow users to query everything, everywhere, all at once?…

Many Jira reporting tools present information through dashboards. Dashboards are not answers. They are assumptions — representations of questions someone decided in advance were important. Once those assumptions are fixed, every other question becomes harder to ask. If you’ve ever opened a reporting screen and wondered…

If you work with Jira long enough, you’ll repeatedly hear terms like Cycle Time, Lead Time, and even “Time Between Statuses.” Agile literature offers conceptual definitions, but when these ideas hit real Jira workflows with many statuses and many local conventions, the meaning of any metric becomes determined almost…

Managing asset information in Jira Service Management frequently requires more than just seeing the current state of an object — teams also need insight into how assets have changed over time. As organizations adopt automation, AI-supported decision-making, and data-driven workflows, the expectation is clear: users want…

I have a post function where I create an attachment and attach it to the issue. The attachment contains information from assets. In order to obtain the assets information I am using the assets API call this way: I created a token and declared as def ASSETS_TOKEN = "xxxYYY..." def auth = "<my personal valid…

I have to define a custom field of type Assets Object, that will fetch all objects in a schema that have no children. The schema defined object type Alpha that have children objects of type Beta and Gamma. Sometimes the Gamma child was detached from the relationship. I want the custom field of type Asset Objects to fetch…