Natalia_Kovalchuk_SaaSJet_ Community Champion

Hi @Gani Siddiqi ! Unfortunately, Jira Cloud itself doesn't have a restore option that allows to easily recover the deleted issues. If the issues were deleted in Jira, you can either try to restore them from a backup or contact Atlassian support. If you are considering the options to prevent such a situation in the future…

Hi solo levelling! Unfortunately, JQL can't help in such a case. As a workaround, I recommend trying Issue History for Jira (Work Item History) app by SaaSJet. The app helps track Jira issue changes, including comment history, in a structured way, with filtering and export options, making it easier than manually pulling…

Hi @Jules McCool ! Unfortunately, Jira doesn't provide JQL that returns all issues moved from one project to another. You can check the history of each issue manually, but it's a time-consuming process, especially when you need to check a great number of issues. I can recommend you try Issue History for Jira (Work Item…

Hi @Dharani Dharan D ! Unfortunately, Jira doesn't provide a restore option for deleted issues. If they were deleted, the options are to restore them from a backup or to contact Atlassian support. If you want to prevent such a situation in the future, I recommend using Issue History for Jira (Work Item History) app from…

Hi Marc Schütz, Unfortunately, Jira doesn't have a native restore option for deleted tasks. If the task in Jira was deleted, the options are to restore it from a backup or contact Atlassian support. To prevent such a situation in the future, you can try using Issue History for Jira (Work Item History) app from SaaSJet.…

Hi @nagata shumpei! If you are considering using apps from the Atlassian Marketplace, I recommend trying Issue History for Jira (Work Item History) from SaaSJet team. It lets you export all your issue data directly to Excel with full control over fields. With the help of this app, you can: Export multiple Jira issue…

Hi @erum s ! If the ticket was deleted in Jira, you can try to restore it by asking your site admin (to use a backup). You can also try to contact Atlassian support. Unfortunately, Jira doesn't provide a native restore option for deleted tickets. To prevent such a situation in the future, I can recommend that you use Issue…

Hi @Santhosh Gosula , This guide may be helpful in your case: https://support.atlassian.com/jira-cloud-administration/docs/export-issues/ The backup process depends on your Jira (Cloud or DC). In Jira Cloud, backups may include data from all projects, including attachments. In Jira Data Center, attachments will not be…

Hi Evie Z! Thank you for the clarification. I will take this into account. But what about linking to our support documentation in Confluence? In many cases, such links help users to better understand the cases mentioned in the article.

Hi @Annette Steinrücken ! Ensure that you choose Fix Versions field in the Columns menu of the filters. Then, go to Export and choose Excel CSV - my defaults. Also, you can try to use Issue History for Jira (Work Item History) app from SaaSJet team, if you are open to considering the usage of other solutions for exporting…

Hi Jamie Edmondson ! Thank you for your feedback. Really glad that you found this article useful. 

Hi 手塚 忍! The easiest way to export history from JSM without using JQL is to use a third-party app from the Atlassian Marketplace. For example, you can try to use Issue History for Jira (Work Item History) app by SaaSJet team, which lets you: export data across your projects without writing complex JQL filter tasks (choose…

Hi @nagata shumpei ! This doesn't look like a data volume problem. I suppose that can be a configuration or permission-related problem. Especially since it started right after enabling Atlassian Guard. I suppose that Guard can restrict data export actions depending on policies. Check whether there are any export…

Hi @jason_roberts! As a workaround, you can try to use Issue History for Jira (Work Item History) app provided by SaaSJet team. In your case, it helps solve exactly the limitation you’ve run into with Activity Stream. In the app, you can use the filters (by space, JQL, etc.), set the needed date range (e.g., Last 14 days),…

Hi @Prasanna Subramaniam! This is a great question, and honestly, it isn't so easy to do this using native Jira functionality. I recommend trying Issue History for Jira (Work Item History) app from SaaSJet team to retrieve the list of your stories that were already closed but moved across multiple sprints before they were…

Hi Bill Sheboy! Thanks for such a clarification. Yes, you are totally right that it is possible to use the WAS IN operator in JQL. What I meant is that when you run a query like <em>assignee</em> <em>WAS IN (...)</em>, the Assignee field still shows the current user, not the one who worked on the task earlier. For example:…

Hi @Babar Brohi! I can recommend you try Issue History for Jira (Work Item History) app by my team. In the app, you can use a JQL filter like: parent = EPIC-KEY. This will show all tasks related to the specific Epic. For example: Using the app, you'll be able: see all child tasks in one place view their current status and…

Hi @Abhisek ! You can't do this using only JQL, as it can show only the current assignee and the current task status. To find out which bugs a developer worked on in a specific sprint, you need to check the change history. One way to do this is using apps like Issue History for Jira (Work Item History) by SaaSJet team.…

Hi @Marcia Peterson ! As you need to export only project issues, their history, comments, and attachments, a full project export may not be the best option. To avoid mixing data, I think that it’s better to export only issues from your project. The problem is that Jira’s built-in export doesn't include full issue history…

Hi @May Reuven ! It looks like something in Jira is still updating the status of your work tickets in the background. The most common reasons for that are automation, connected integration, webhooks, or dev-related actions. You can check the native Jira ticket history (History tab) to understand exactly what changed, when…

Hi @Doug Smith ! Jira stores the full history of every task, but it isn't so easy to see a clear timeline of who was responsible for the task and for how long. You can open the History tab in the work item and explore the changes. Also, I can recommend you try much easier way to see this by using Issue History for Jira…

Hi @Oliswa Accom ! Tickets in Jira can be deleted, but only users with the permission to delete can do so within the project. If a ticket in Jira is deleted, it can't be easily restored easily, as Jira itself doesn't provide that functionality. However, you can track the deleted tickets in Jira with the help of the Audit…

Hi @ckopanon! Unfortunately, JQL can't show every update that was made by a specific user. It only shows work items that were updated, not each change separately. It means that if the work item in Jira was edited a few times by the same user, JQL will still show it only once. In your case, I can recommend you try Issue…

Hi @d852673 ! Unfortunately, Jira doesn't have a native option that allows restoring deleted tickets. You can try to ask your site admin to use a backup or contact Atlassian support. To prevent such a situation in the future, you can try using Issue History for Jira (Work Item History) app from SaaSJet team. With the help…

Hi @Sidra Shakoor ! If the Jira ticket was deleted, you can try to restore it by asking your site admin (to use a backup) or contacting Atlassian support. Unfortunately, Jira doesn't provide a native restore option for deleted tickets. To prevent such a situation in the future, you may consider using Issue History for Jira…

Hi @Spencer Hudson ! In case you are using Confluence macros, I can also recommend that you look at this article: 5 Most Useful Jira Macros in Confluence (With Practical Use Cases) Hope you find some useful info there. 

Hi Elena_Communardo Products! Thank you for your feedback!

Hi s_gridnevskii! Yes, it is possible to get Jira work item history using REST API; however, it will be much more complicated than, for example, using Issue History for Jira (Work Item History) app. Using the Jira API means writing scripts, managing authentication, handling pagination, and building logic to extract…

Hi RG! If you need to export all issues from a particular project in Jira Data Center, including all fields and comment history, I recommend you try Issue History for Jira (Work Item History) app from the SaaSJet team. Using it, you will be able to do the following: Export full comment history (who added, edited, and when)…

Hi, @Lira Martynenko ! You can take a look at some gadgets for Jira dashboards. For example: Pie Chart gadget. It can allow you to see the distribution of tasks by status, assignee, priority, etc. Sprint Health gadget. Using it, you can get a simple snapshot of sprint progress. Activities gadget by Issue History for Jira…