Natalia_Kovalchuk_SaaSJet_ Community Champion

Hi @Ayush Pathak ! I can recommend you try Issue History for Jira by SaaSJet, which tracks all changes to Jira work items over time. It provides the Security Scanner View (PII & DLP), which automatically scans Jira work items and their complete change history for sensitive data such as passwords, credit card numbers,…

Hi Lurae Criswell! I suppose this can happen because Jira sometimes records internal or background updates that aren't visible in the work item itself. In other words, Jira may log some small technical actions even when the status didn't really change back and forth. If you need a more advanced, easier way to track Status…

@Jens Schumacher - Released_so , Great! Thank you! )

@Mia Tamm _Simpleasyty_, great point about Confluence! 👍 Really, bringing exported data, with the help of Issue History for Jira, directly into team spaces can help keep reports accessible and actionable.

Hi @Bill Zhu! Unfortunately, Jira doesn’t provide a native functionality that allows restoring deleted issues. Once it is deleted, it’s permanently removed from the project and can't be restored selectively by the project. Only a full backup is possible. However, as an alternative option, I can recommend trying Issue…

Hi @Eli Vazani ! Unfortunately, Jira doesn't have a single option to export all project information, such as work items, comments, attachments, etc., in one click. However, you can try other ways. For example: * Export of work items and project data - you can use native Jira options and export such data in CSV, Excel, or…

Hi @arizal_bukalapak_com , Such an error can occur because of a large export size. You can try a smaller export. Or you can also use a different browser. If the error repeats, it is better to raise a support ticket with Atlassian. If you need to export Jira issue history or custom reports, you might also take a look at the…

Hi @HaRsHaS_ V! I propose that you try such a JQL query: fixVersion = latestReleasedVersion() AND status NOT IN (Done) and updated <= -5d Using this JQL, you can retrieve a list of tickets in the latest released version that are not marked as Done and haven't had any updates (including any change to status, comment, or…

Hi @Sherwin Soriano! Unfortunately, this information is not available using native Jira JQL only. Jira standard JQL can only show the current value of the Sprint field, not the past changes. With JQL, you can get such data: * Tickets currently in a sprint: sprint = "Sprint Name" * Tickets that were in a sprint (if the…

Hi @shiva kumar Gosul ! Unfortunately, JQL in Jira does not support searching or exporting the comment history of multiple issues directly. I recommend trying the Issue History for Jira app from my team. It can help you to view, filter, and export all comments (along with other issue changes) in bulk in Excel or CSV…

Hi @Muammad Faizan Iftikhar , Yes, Jira fields can only hold one value at a time by default. As a workaround, you can try using the Issue History for Jira app from my team if you are considering third-party apps. Using it, you can do the following: * Track every change made to issue fields over time. * View what the value…

Hi @Gaurav Tiwari, As I know, JQL doesn't allow searching based on historical status changes. Therefore, it is not possible to get a list of all issues that were reopened at any point during their lifecycle. Using the query ' status = Reopen' only shows issues that are currently in this status. I can recommend Issue…

Hi @Christopher Diaz ! If we are talking about tracking comments in Jira, here are a few possible approaches: Jira Query Language (JQL). Using it, you won't be able to filter or count comments, but you can try searching for issues you've interacted with and manually check comments. Here is an example of a JQL query that…

Hi @Mohith Tummala , If I understand you correctly, you need to get the exact date of multiple issue status transitions. I recommend trying Issue History for Jira app from my team. It allows filtering specific status transitions of epics and issues, as well as viewing their exact date and time updates. In case you need the…

Hi @Josephine Benjamin ! I think you may try to do the following: * Look at the history of the issue. Open one of the issues and go to the tab called “History” to find out when and how it was moved. This will enable you to know which sprint it belonged to. * Recreate the removed sprint. You can create a new sprint manually…

Hi @Charles Brooks! Unfortunately, Jira automation doesn't currently support exporting data directly to a CSV file. I think you can try to write a Python script that uses the Jira REST API to query your project data. With a combination of JQL and the API, you can try to pull specific fields from issues and export them to…

Hi @thumuluru_shreya , From the screenshot you added, I see that you are using Issue History for Jira app, which was developed by my team. You can export any ticket activity individually (PDF, CSV, Excel) or the history of multiple tickets altogether with the help of this app. If you need to export only one ticket, go to…

Hi @pvala_micron_com! JQL has some limitations when it comes to date range filtering, particularly in combining multiple conditions simultaneously. However, you can try to use such JQL queries in your case: * To get the list of issues that were created between two dates: creator = currentUser() AND created >= "2025-01-01"…

Hi @Pedro Webster, You can use a custom field and Jira automation or check apps for this case. Issue History for Jira, developed by my team, enables tracking past changes for any field, including the Flagged field. You can select any time range simply from a calendar drop-down or presets. Also, this article (the last two…

Hello @Shwetha Sundaramurthy , Yes, it is possible to log multiple time entries on a single sub-task in Jira. Jira has native time tracking, which means you can add multiple work log entries over time by simply clicking Log Work. If you're looking for an easier way to track time, I recommend trying the Time & Cost Tracker…

Hi @gopal guna , As I know, Jira doesn't provide a native REST API to track deleted issues. As deleted, issues are permanently removed from the system and aren't stored in a retrievable way via the standard API. However, you can use third-party apps available on the Marketplace for this purpose. As an example, you can try…

Hi @Ayşegül Yavuztürk , Try to check if time tracking is enabled. Go to Jira Settings → Work items → Time Tracking and ensure that it is correctly set for your instance. Also, you can check the users' permissions. If a Time tracking field is not working in your project, you can go to Project Settings → Work items → Fields…

Hi @Earl Jane Baton ! You are using Time in Status app from SaaSJet team. Please get in touch with the Support, and they will help you fix this problem. 

Thanks!

Thank you!

Thanks a lot!

Thank you so much)

Thank you! )

Hi, asadiq!Welcome to the group!It is a place where marketers exchange tips on how they plan campaigns, manage content, and collaborate more effectively using Jira, Confluence, and other tools. You will be able to share templates, ask questions, and find out best practices used by others.It is also an excellent place to…

Hi MattD! The main value of the Bulk Revert functionality of Issue History for Jira app is to roll back changes by one step. However, if you only need to clear field values, Jira native Bulk change is sufficient for that.