Natalia_Kovalchuk_SaaSJet_ Community Champion

Hi @Seung Yeon Han , According to Atlassian's documentation, deleted work items are logged in the Jira admin audit log. You can search for a deleted work item by its key and see who deleted it and when. The Audit Records API allows you to get audit events. I'd suggest trying it out with a known deleted work item to verify…

Hi @K, Padmashri [C] Once you've migrated to Jira Cloud, you can still connect your Jira data to Power BI. You'll just need to set up a new connection to your Jira Cloud instance. There are a few ways to do this: 1. Use a Power BI connector for Jira Cloud. There are a number of Marketplace apps that let you connect Jira…

Hi @Kim Clark, If you need the full details related to individual worklog entries, you can try to use the Jira REST API: GET /rest/api/3/issue/ABC-123/worklog More details can be found here: Atlassian REST API - Get issue worklogs Another option is Issue History for Jira (Work Item History) by the SaaSJet team if you need…

Hi @Tom George Menachery! Here are a few things I'd suggest checking: Try a different network (e.g., a mobile hotspot). As I know, Atlassian has documented instances of Jira exports failing due to some connections being blocked by network settings. Try exporting fewer work items. Narrow your JQL filter and see if a smaller…

Hi! Can't open the full-size image in the articles:

Hi @Emma Phillips ! I think it is probably the most difficult aspect to deal with the old data problem; although permissions and user awareness can help stop sensitive data from being added, they won't inform you about what is already concealed in the old Jira work items or comments. With Jira Cloud, you can try the…

Hi Xenia Chilkowich , Sprint +1 can be really frustrating when you want to see the actual sprint names directly in Jira rather than having to open each work item or export the data to Excel. You can try to use Issue History for Jira (Work Item History) app by SaaSJet. In the app, you can add the Sprint field as a column to…

Hi sundeepkothurthi , Using Issue History for Jira (Work Item History) app by SaaSJet, you can see what a work item looked like at the moment it was created and then keep track of how its field values changed afterward. With the app, you can select the project and the date range that you want, and then locate the work item…

Hi Mahanth Prudhvi P , Great questions! I would probably approach Jira Cloud disaster recovery as a combination of Atlassian's native backup capabilities + a documented recovery process + work item history/recovery tools. What is important is that "backup" and "recovery" should not be regarded as identical. It is useful to…

Hi Utkarsh Chandel! In large Jira instances, this is certainly a problem. Sensitive info can not only appear in current Jira work items but also in old descriptions, comments, and other fields, since no one remembers that it exists. A way to deal with this is to periodically check the Jira content for sensitive data rather…

Hi Utkarsh Chandel ! I think that the scanning frequency should be based on the sensitivity and the risk level of the data rather than using the same schedule in all cases. High-risk Jira projects will need to be monitored much more frequently, whereas those with lower risk can be looked at periodically. For Jira, you…

Hi @Svetlana Mandrosova ! Yes, this is the kind of case where you need historical Assignee and Status data, not just the current Assignee value. With Issue History for Jira (Work Item History) by SaaSJet, you can create a report that shows who was assigned to a story when it was in a specific status. For example, in our…

Hi @Jay Sharma ! If you are open for using third-party apps, I can recommend you trying Issue History for Jira (Work Item History) by SaaSJet to see what happened and possibly recover the affected Sprint values. In the app, filter the history by the Sprint and the date of the workflow update. This will help you find out…

Hi @Harshad Prajapati ! Yes, you can create this type of report using Issue History for Jira (Work Item History) from the SaaSJet team. In the app, you can select the required project or sprint. Then, use the Column option to include the fields you want, like Sprint and Fix Version. The report will display historical…

Hi @Bing Ren ! 21 CFR Part 11 compliance isn't determined by just one Jira report. Auditors usually look for a mix of technical controls, documented procedures, access controls, and audit trails. Jira Cloud offers features like the Jira Audit Log, permission schemes, and Atlassian's compliance documentation. However, if…

Hi @Nicoleta Mircea , If you are open to using apps available on Atlassian Marketplace, I recommend trying Issue History for Jira (Work Item History) from the SaaSJet team. This app is used by many companies in highly regulated industries that need to prepare for internal or external audits such as ISO 27001, SOC 2, and…

Hi @Amita Sharma , Unfortunately, Jira doesn't provide native restore functionality to recover deleted tasks. If the task in Jira was deleted, the options are to restore it from a backup or try to contact Atlassian support. To prevent such a situation in the future, I can recommend you try Issue History for Jira (Work Item…

Hi @Emma Handley , Yes, unfortunately, Jira Cloud doesn't offer a built-in way to view the exact status of tickets from a specific time in the past. If you are open to using third-party apps, I can recommend Issue History for Jira (Work Item History) from my team as a workaround. With it, you can do the following: * Filter…

Hi! Alexandre Pezzini, thanks for recommending Issue History for Jira (SaaSJet). slucchesini, really, the app provides Field changes duration report that automatically calculates the time difference between the selected field changes available when downloading reports using the Excel (Advanced) export. Here is an example:…

Hi Peter von Weissenberg! Using native Jira functionality, it is impossible to restore the deleted work items. With the help of the Jira Audit log, you can see that the work item was deleted and who was responsible for such an action. To be able to restore the deleted work items in Jira, it is recommended to use an app…

Hi Anwesha Pan! Thanks! I am glad that you found it helpful. 

Hi Viswanathan Ramachandran, Thanks for sharing! I completely agree. Improving Jira can go beyond just performance. It can also help create a cleaner, more secure, and easier-to-manage environment.

Hi @Fabricio Riveros! I suppose that Jira Cloud doesn't have a built-in method to report all these metrics. If you need to track Sprint field changes over time, a history tracking app can help. For example, Issue History for Jira (Work Item History) app by SaaSJet helps to track every Sprint field change. You can see when…

zoltanersek _outpostlabs_dev, thanks! Yes, it's great that AI can help us gain valuable insights and improve the effectiveness of our work. 

Hi Marie -Teamlead-! I completely share your frustration. 😊 Today, traffic is no longer one of our main performance indicators because the numbers often don't reflect the reality. We consistently use UTM parameters across all our external channels, like community articles, social media, partner campaigns, and newsletters,…

Hi @Vlad Mo ! I don't recommend deleting and recreating the issues. This will create new issue keys. You would lose the original issue history. I think a safer approach would be to update the existing issues with Jira Automation or the Jira REST API. If you're looking for a way to find all affected records and keep the…

Hi @Martin Vali ! Unfortunately, Jira dashboards only show the current state of tickets. They don't provide historical snapshots. For this kind of historical trend analysis, I suggest using Issue History for Jira (Work Item History) app by SaaSJet. With the help of this app, you can generate custom reports related to Jira…

Hi @Sathish Kumar ! Unfortunately, using Jira JQL alone, you won't be able to filter comment updates from a specific team or users during a specific time period. While JQL can help find recently updated tickets, it doesn't give detailed reporting on comment history. In this situation, I recommend trying Issue History for…

Hi @paul ! You can find some of this information through Jira's built-in reports and work item history. However, Jira doesn't offer an easy way to report when an epic enters a specific status, when it leaves that status, or how long it remains in each status across multiple epics. For a single epic, you can check the…

Hi @Syeda Raeesa Batool ! It's much easier to handle large Jira projects when teams have a clear structure, consistent processes, visibility, and historical tracking from the start, especially when multiple teams, sprints, and stakeholders are involved. Some of the following practices can be really effective: * Structure…