Petru Simion [Simitech Ltd.] Atlassian Partner

Hi @Flester Iulian , What you’re trying to do — ingest complete Jira data including all comments, worklogs, and full changelog/history for large instances — is not straightforward with the standard Jira REST APIs. As you’ve noticed, the Search API truncates nested fields, paginating comments and worklogs, and…

Hi @hhasan , That usually happens when comments are exported through tools that don’t handle Jira’s rich-text / formatting properly, so Excel ends up showing placeholders (like hyphens) instead of the actual content. If you’re using a third-party app or a custom export, the issue is almost always in how comments are parsed…

Hi @Divya Sudhakar _US - ADVS_ , Just to set expectations: calculating metrics like Issue Age and Time in Status in Jira Cloud isn’t straightforward out-of-the-box. Jira’s default reporting doesn’t store these durations in fields you can simply pull with JQL or native automation. You’d need to track status transition…

You are welcome. Our team quickly implemented this new report type because you expressed a need for it. Regards, Petru

For anyone who found this article useful, I’ve since added a related enhancement to the same app: Issue Snapshot. It lets you reconstruct how an issue looked at a specific point in time — effectively a full field snapshot, not just transitions — which complements Issue History analysis nicely. I’ve written a short article…

Hi @Shikhar Sharma , For exactly this type of investigations you can use Versions Usage For Jira released by our team. It allows you to search the version usage across all your projects. If you want to see what versions were released for example during 2024 you will perform a search like this: The result is exportable in…

Hi @VINCENT DUPONT , You can look at the history if each issue. If you need data about multiple issues this could be a tedious task. Alternativelly you can use Issue History Reporter for Jira an app built by our team . Select Report Type: Issue Snapshot, and the Issue Snapshot Date: Select the date and time you are…

Hi @Cynthia Schulz , While finding who assigned you one ticked is feasable, by using the History, if you want to have an overall view of who assigned all your tickets, you can use Issue History Reporter for Jira (Work Item History) , an app released by our team. You can search by various criteria and export your result in…

Hi @Christopher Brown , If you are open to using apps, you can use Assets History Reporter for Jira , an app released y our team. You can search your assets by various criteria and see what was changed and by whom. The result is exportable in csv format. You can later agregate multiple searches in your csv file for Excel…

Hi @Suraj Pawar , you can track progress by looking at how a single issue transitions through statuses, but that only works one issue at a time. Where teams usually struggle is getting an overall picture. Jira’s built-in boards and reports (Scrum/Kanban boards, burndown, control charts) are useful for beginners to…

Hi @Hagit Nagola Shaham , If you are open to using apps you can use Fields Usage for Jira , an app released by our team. You can see which fields are used in projects either via screens: Or workflows: Regards, Petru

Hi @Devarajan Mani , This is a really common challenge after migrating from Server to Cloud — especially when the site has grown over time. Roles often accumulate gradually and, after migration, you suddenly realise there are dozens (or hundreds) that are either unused, duplicated, or unclear in purpose. Before deleting…

Hi @Gregg Gellhaus , This sounds like a great initiative 👏 — once teams start working more cross-functionally, clarity around who owns what becomes just as important as the work itself. I really like that you’re splitting the Roles & Responsibilities play into two sessions. In my experience, the first pass surfaces…

Hi @Sara Innes , Field cleanup in long-lived / migrated Jira sites is always tricky — especially when you also have retention requirements. And you’re absolutely right that simply searching for “field X is not empty” won’t always tell the full story, because: ✔ Archived projects are excluded✔ A field may still be…

Hi @Danielle Alota , If you are open to using apps you can use Assets History Reporter for Jira , released by our company. You can search for your assets using the filter values, visualise and export to csv. Regards, Petru

HI @Raheem Pillay , While you can automate the solution for one asset, if you need an overall view over your assets you can use Assets History Reporter for Jira , an app released by our company. You can search and export your data. Regards, Petru

Hi @Zoe N_ , On company-managed “software” boards, the Days in column feature works because each board column represents one or more workflow statuses — so Jira is really tracking how long the issue stayed in the statuses mapped to that column. In a company-managed business project, that specific “Days in column” toggle…

Hi @David Martínez López , In Jira Service Management Cloud, the time between statuses — and the total cycle time — depends on how your workflow is designed and when an issue is considered “resolved.” Jira itself doesn’t define cycle time for you, because every organization structures workflows differently. So the key idea…

Hi @ckopanon , Each organization defines its own workflows in Jira, so “time to resolution” really depends on how your workflow is designed and when the Resolution field is set. In Jira, the Resolution field has two fundamental states: Unresolved → the issue is still open Any other value → the issue is considered done So…

Hi @Giridhar Ujjinappagari , You can write a scripted field that can derrive the time between statuses. It will be some extensive work. If you are open to using apps, you can use Time in Status Reporter for Jira an app released by our company. You will be able to see how long the issue spent in each status and according to…

Hi @Raheem Pillay , I will suggest some of the apps released by our company. They all allow you to filter your search and export it to csv. Our approach is simple: we provide raw, structured data and let you use it in the way that best fits your needs. In an AI-driven world, raw data is extremely valuable. It allows you to…

Hi @Ganesh Kumar Vary , If you are open to using apps, you can use Roles Dashboard for Jira , released by our company. You can see clearly which user is assigned to which role and in what project across your organisation. Regards, Petru

I’ve been thinking more about the topic of rework and how often it goes unnoticed in workflow metrics. One thing that becomes clear when you look at raw time-in-status data is that identical Cycle Time values can hide very different process behaviors. In a future article I’ll explore how teams can use loop counts and…

Thanks everyone for reading. In a follow-up article I’ll go deeper into the practical side: how teams can group statuses into their own cycles and derive metrics like Cycle Time, Lead Time, QA Cycle, or Wait Time using simple Excel formulas or pivot tables. The idea is to show how flexible and transparent these…

Hi @mborinstein , This deppends a lot on how you set up your workflows . You need to define what "each engineer spends on a ticket". Once you defined this you can write your own app that will extract that data. If you are open to using apps you can use a mix of these two apps, both released by us. Issue History Dashboard…

Hi @Ashraf B , You will have to either write your own app using Forge or Connect or if you are open to using apps you can use Time in Status Dashboard for Jira released by us. You can filter using various criteria or display all results for a project without filtering if you wish. You have access to two data perspectives,…

Hi @kkostic , If you are open to using apps you can export using Time in Status Dashboard for Jira , one of the apps released by our company. You can either search for all result by project or filter using the available fields and Export as CSV. You can chose between the two perspective. Columns Perspective Rows…

Hi @Nihar Sharma , If you are open to using apps you can use one, or both of the following apps, released by our company. Issue History Dashboard for Jira (Work Items History You can searcy by project, assignee, reporter. Roles Dashboard for Jira You can search using two perspectives. User-Role-Project Perspective…

Hi @sunil Kumar BV , If you are open to using apps you can use Time in Status Dashboard for Jira an app released by our company. You have two perspectives to analyze how much time was spent in each status and also how many times an issue was present in each status. You can export to csv and use Excel to sum up values as…

Hi @Brad Schultz , If you are open to using apps you can use Time in Status for Jira , an app developed by our company. You can filter by various criterias, and you can view, sort and export to CSV your search result that comes in two perspectives, both disclosing how many times the issue was in each status. Columns -…