Petru Simion [Simitech Ltd.] Atlassian Partner

Hi Flo, Another option for retrieving the previous description is Issue History & Snapshots Reporter for Jira, an app I developed. It allows you to inspect historical issue changes, view an issue snapshot at a particular point in time, and compare snapshots to identify what changed. This can be useful when a description…

Hi Utkarsh, With 800+ Jira projects, reviewing project-role assignments individually is clearly impractical. One useful approach is to analyze role assignments in both directions: Project → Role → Users/Groups User/Group → Roles → Projects The second view is particularly useful for access reviews because it helps identify…

Hi @sundeepkothurthi , Since the ScriptRunner operation overwrote the field values, if those changes were recorded in the Jira issue changelog, the previous values should still be available as the old values of those changes. For multiple affected issues, you can use Issue History and Snapshots Reporter for Jira to search…

Hi @joao zampa , One additional piece that may help with the Jira configuration side of this problem is Fields Usage for Jira from Simitech. Full disclosure: I am part of the team that releaqsed the app. Fields Usage for Jira traces where fields are actually used across Jira configuration, including: Field → Screen →…

Hi @Svetlana Mandrosova , Yes, this can be determined from Jira's historical data. As mentioned above, you can extract the changelog through the REST API, or manually inspect the history of an individual work item. The basic idea is to determine when the work item entered "In Testing" and when it left "In Testing", and…

Hi @Kristy , Unfortunately, Jira doesn't currently provide a way to limit the "Add users to a role" drop-down to only the roles that are used by the selected project. Since project roles are defined globally, the list always contains every project role in the Jira instance, which can become quite long in larger…

Hi @Nicoleta Mircea , In my experience, preparing change management evidence is usually about two different types of change, and both are important during audits. 1. Configuration change evidence This answers questions like: What was changed in the Jira configuration? What was the impact of the change? Where is this…

Hi @MeghnaP_LogicLemur Labs , Congrats on the update! A continuous Site Health Score is a great feature—having high-level visibility during quarterly reviews is definitely half the battle. That said, in our experience working with scaling instances, watching the metrics is one thing—determining what to actually do about…

HI @Martin Vali , Hi, If you're open to considering a Marketplace alternative, this is one of the use cases Issue History & Snapshots Reporter for Jira was designed to solve. Disclosure: I'm part of the team that developed this app. Jira dashboards report the current state of issues, but historical reporting is much more…

Hi @Elaine Beckford, If you're open to considering a Marketplace alternative, you may want to take a look at Time in Status Reporter for Jira. Disclosure: I'm part of the team that developed this app. One of the features that may help with your use case is that you can choose the time format used in the report. For…

Hi @AGASTYA SHARMA , One aspect I haven't seen mentioned is that governance isn't just about deciding whether to create a new field—it's also about knowing which existing fields can safely be removed or consolidated. In many mature Jira instances, the biggest challenge isn't having 500 or 2,000 custom fields. It's…

Hi Maurice, Unfortunately I don't have visibility into Atlassian's roadmap, so I can't comment on whether this functionality will be added to Assets in the future. At the moment, native Assets provides history at the individual object level, but does not provide bulk historical reporting, historical ownership searches…

Hi @Maurice Adams, For an individual asset, you can review the object's History tab in Assets to see attribute changes over time, such as ownership updates, provided those changes were tracked in the object attributes. However, the native Assets interface is primarily designed for investigating one asset at a time. If you…

Hi @SHREE MUKKHI R RAJADURAI , If your goal is primarily reporting and exporting project role assignments rather than building a custom solution with REST APIs, SQL queries, CLI scripts, or Rovo, another option is to use a reporting app. For full disclosure, I am part of the team that built and released Roles Usage for…

Hi Bartek, Thank you for the detailed response and for sharing those examples. I agree that advanced JQL functions can help answer many Time Analysis and Audit-style questions, especially when the goal is to identify issues matching specific historical conditions or transitions. The Point-in-Time State question is the one…

Hi @Iacob_ Vincențiu Mihail , What you are trying to answer is a bit more complex than just checking whether a user appears directly in a project role. In Jira Cloud, a user can effectively have access to a project in multiple ways, for example: by being assigned directly as an actor in a project role by being part of a…

Hi @Nathan Vinicius Vital Santos , Just to add some clarification here — that KB is about the “Jira environment import” into Assets, but it doesn’t really cover this use case. It can bring in some high-level config (projects, workflows, etc.), but it doesn’t show: which custom fields are used per project how fields are…

Hi @Nathan Parfitt , The same question:m Which of the apps are you reffering too. If you use Time in Status Reporter for Jira please send a message to admin@simitechsoft.com with the details Disclosure - I work for the company tha released the application. Regards, Petru

Hi @Mary Doherty , If you're trying to measure Cycle Time from “In Progress” to “Done” for each Story, you're not missing anything — Jira does not offer a straightforward built-in way to calculate and list that duration per issue. Jira records status changes in the history, but it doesn’t natively compute the elapsed time…

Hi @Lira Martynenko , Yes — this is a very common requirement, and trying to solve it with multiple automation rules usually becomes unreliable and overly complex (especially when handling reopens, loops, workflow differences, and roll-ups). Instead of building and maintaining ScriptRunner logic, you can achieve this much…

Hi @Ashwin Kurundkar , If you need to calculate how long a Bug issue spends in each workflow status — including transition timestamps and total time across multiple statuses — Time in Status Reporter for Jira released by our tem, isbuilt specifically to answer this. The app reads the full issue history and calculates: Time…

Hi @Álvaro Boza , On the left hand menu look for Scripted fields. You will need to create a script that will be executed when the field renders. For that you will need to add your field to screen -> screen scheme -> issue type screen scheme -> Project. Script Runner provides you wihe examples how to code your script.…

Hi @Álvaro Boza , You can do this by creating a scripted fields, using Script Runner app. You will loop through all epic children and sum up their logged time into this scripted field that will always display the total. The good thing is that it works for future and already existing epics/children. Regards, Petru

Hi @Richard A_ Michaels , Jira Cloud does not provide an API to search versions by name. Versions are project-scoped, so the same release name can exist in multiple projects with different IDs, and the REST API requires you to already know the project (or enumerate all projects and scan their versions). If the goal is…

Hi @Flester Iulian , Update: since this answer was posted, we’ve released Issue Insights for Jira, which bundles the three apps mentioned above into a single offering: 👉 Issue Insights for Jira The bundle includes: Issue History Reporter for Jira (full changelog and point-in-time issue snapshots) Time in Status Reporter…

Hi @Ashwin Kurundkar , You can do this one issue at a time by creating a calculated field; however, calculated fields are evaluated per issue and cannot aggregate or divide the results of multiple JQL queries. To show this kind of percentage on a dashboard, you need a gadget or app that supports aggregated calculations…

Hi @Urmila Ghosh , You can do this in Jira, but it depends how efficient and detailed you want the result to be. Option 1: Check each issue manually (built-in Jira) You can open an issue and go to History / Activity → History to see every status transition (from → to, date, user).This works, but it’s manual, slow, and…

Hi @Aldrine Abisheck , If your goal is to understand how long an issue has actually spent in In Progress—even if it was moved in and out of that status multiple times—there’s a straightforward way to do this. You can use Issue History Reporter for Jira (Work Item History) , an app built by our team.With the Issue History…

Hi @Veena Kunchala , If the description field wasn’t retained during migration, recovering it from Jira history alone is often difficult. Jira history logs usually store change diffs and formatted payloads (ADF/wiki/HTML), not clean rendered text — which is why the values you see now look distorted. In this scenario, tools…

Hi @hhasan , Based on what you described, this isn’t related to Excel and it’s not something you changed. In Jira Cloud, comments are stored as rich text. When you export certain built-in reports to CSV/Excel, Jira has to convert that rich text into plain text. In some reports, that conversion doesn’t always happen…