Yuliia_Borivets_[SaaSJet] Atlassian Partner

Hi @Aiswarya Ayyapan Recovering or tracking deleted issues in Jira is impossible if you don't have a backup. The following actions can help you avoid losing deleted assignments in the future: - Limit access to delete issues to admins only; disable it for regular users. - Back up your projects. - Get the app from…

Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15 Day 16 Day 17 Day 18 Day 19 Day 20 Day 21 Day 22 Day 23 Day 24 ✨

Hi @Johannes Rudolf You can select the specific issue and check its field updates. But if I understand correctly, you need some report that will show all issues in your project and the number of updates for the specific custom field per issue, right? If so, you can get the breakdown of the selected field changes per each…

Hi @Stephan Gans 1) You can check the Activity Stream gadget on the Jira dashboard. It should preserve the table formatting. 2) Another solution is Issue History for Jira from my team. It also shows the original formatting and highlights the updates made. You can also roll back the changes using the Revert option.

Hi @Vasikaran With JQL, you can only search for status changes like status CHANGED FROM "Open" TO "Closed". However, the result will not display additional info (when the issue was created and updated). The report you need can be configured with Issue History for Jira from my team. It displays the full history from the…

Hi @chris_rex My team has also struggled with the description and its formatting, so we added the revert option to the Issue History for Jira app (developed by my team). It allows us to revert changes made to the description. Text formatting (bold, color, lists, tables) will be preserved. The only exception is attachments.…

Thank you! Your feedback is welcome. Have a great day!

Hi @Johannes Rudolf Thank you for your question! It's possible to see the exact number of updates for a specific custom field. This information is available in the field or column manager. You can also set some filters like project and dates to narrow down the result. It looks like this: So, generally, this information is…

Hi @Valliammai Veerappan My team has recently launched an option that helps to revert bulk changes for different fields, including statuses. It's available with Issue History for Jira. You can select any past change and revert it. Learn more about it here: Revert bulk changes

Hi @Mor There is an Activity Stream gadget on the dashboard available for Jira Data Center users. Here, you can filter issues by projects, users, dates and some activities. You can check if it works for you.

Hi @Kuldip Rakhra You can track how tickets move between projects with Issue History for Jira (developed by my team). Here is an example of the report. Just include the required projects with JQL. Read more here: How to track tasks that moved from Project A to Project B

Hi @Aleena It's possible with workarounds like custom field+automation or plugins. For example, you can filter any field with Issue History for Jira (the app developed by my team). Due date changes of a single task: Due date changes for multiple tasks in your project: Read more here: How to see due date changes in Jira

Hi @Frank Clay I haven't found the exact equivalent. You might check "audit log" apps on the Marketplace (maybe the first one here): https://marketplace.atlassian.com/search?query=audit+log&product=jira&hosting=cloud

Hi @Harsha Shridhar In the Cloud, there is a Filter results gadget; I am not sure if it's available for the Data Center. This gadget allows to select issue fields, and with the filter you can get issues updated during the last 6 months. Another solution you can check is Issue History for Jira (Data Center and Cloud) app…

@rmontolio, thanks for your feedback and the question! The DURING predicate requires 2 values so you might try a query like this: status changed to Done DURING (-1d,now())

Hi @Bud Herz You can try something like this: project ="YourProject" AND issuetype = Story AND status CHANGED TO Blocked DURING ("-12M", "now") Here, you might check some other cases: Status transition history for multiple Jira issues

Hi @Richard Cieslik This post shows how to capture the "date of change" for statuses with Jira automation (option 2) and a plugin from my team (option 3): How to capture the “date of change” for Jira issues

Hi @Dave Bair I think the method with custom field + automation might work for you. If you are open to using apps, you can check out Issue History for Jira developed by my team. It provides a separate column and filter for "Updated by" person. Here, I have a similar post: How many Jira issues were rejected after testing?

Hi @Mykhailo Goncharov, You can check Issue History for Jira app from my team. It provides a history of a single issue with highlighted (red and green) changes. It's easy to see what exactly was updated: With additional filters, you can also get changes for a specific field like here: How to get history for the specific…

Hi @Jayanth If you need a daily report of changes for your project, you can check Issue History for Jira (an app from my team). You can customize it and add only a few fields you want to track: Or get the report with all changes per project in one view: It's also possible to send this by email. For scheduling, we have only…

@Lucas Modzelewski _Lumo_ thank you for mentioning Issue History for Jira from my team and the use case. @Rajan Dangol, here is an example of the report: You can book a demo to see how it works or try it for 30 days.

Hi @Bill Sheboy Thank you for your comment and for pointing out these key considerations! There are indeed exceptions when tracking changes. As you suggest, experimenting is key to understanding when these methods will or won’t capture changes accurately.

Hi @Petru Simion _Simitech Ltd__ "As a general guideline, we ask all members to avoid replying to content older than six months. A good practice is to always check the date before responding." Please read and follow the Community rules here:…

Hi @Lori Benowitz Jira automation might work for you to capture a date when the status moves from one to another. Look at the example (option 2) in this article: How to capture the “date of change” for Jira issues Also, you can check a solution developed by my team - Issue History for Jira. It captures "date of change" for…

@Daria Kulikova_GitProtect_io thank you so much!

@Ilona Maras _ Communardo Products, Happy to hear that! Thanks for your feedback!

Hi @Maggie Soria I think some of the options suggested by Bill, such as custom fields and automation, might work for you. If you are open to using add-ons, you can check the one developed by my team. Issue History for Jira provides a separate column that captures the date of change for any field. In this case, we can add…

Hi @Vishal Biyani You can only identify deleted issues if you have backed up your project. To prevent a loss in the future, you might consider possible solutions like backup or apps from the marketplace. With Issue History for Jira (the app is developed by my team), you will be able to identify both deleted issues and…

Hi @Scarlet I'm not sure how to solve this with automation, but you can check a solution from my team in this article How to get deleted comments in Jira? It shows what comment was deleted, when, and by whom.

Hi @Amit.Kumar3 If you want to capture assignee changes, you can check the Issue History for Jira app developed by my team. Here, you can create a report showing the ticket number, all assignee changes, and the dates of changes. Report example: This report can be created to check the change logs of any issue field.