Comments
-
Hi @[deleted] It's possible to create a change log table for the list of issues. The case you've described is the reason why our team developed Issue History for Jira. The app helps to create the report you need. Just add any standard or custom field to the grid's columns. Here is an example of how it looks: There is…
-
Hi @Rob Crick It seems there is no way to prevent Jira issue from editing. But your data won`t be lost – you can always check what was updated in the issue history. If User 1 and User 2 have made some changes, it will record each of them. Also, you can check the app from my team – Issue History for Jira. It's easy to…
-
Hi @sagar Nice to have you here! You can find some helpful info in the article: How to export issue history from Jira? If you're on Cloud, you can try to monitor the full issue changelog with Issue History for Jira app. My team developed it as a journal for every past activity. Check out if it can help you.
-
Hi @Akshithrekulapelli If you want to track issues that moved from one project to another, you can check this article with a similar case: How many tickets were moved from one Jira project to another? [Use case]
-
Hi @ConstantinaLucia.Marin This article has some suggestions for your case (you can try to get ticket history via REST API): How to export issue history from Jira?
-
Hi @rob_vandersteen I'm not good with JQL, so I can suggest an alternative solution from my team – Issue History for Jira. It allows you to filter tickets by the date range. Just select appropriate dates from the calendar – and you can monitor all past status changes.
-
Hi @[라이브_PM] 차승연 If you need to get a changelog of the fixversion field in one report, you can check Issue History for Jira. My team developed the app as a journal for all past activities. You can easily filter issues by project, sprints or date range here. Just include fixversion to the grid's columns. Here is an example…
-
Hi @Paiton Swaim If you're looking for a customizable report, check out Issue History for Jira. My team has developed an app as a journal where you can monitor changes for any standard and custom issue fields. You just need to include those fields in the grid columns. You can filter issues by projects, sprints, assignees,…
-
Hi @Dorothy Callahan You can find issue key changes in the History while opening the Activity section like on the screen below. If you need to get a report for the list of issues or filter issues by sprint, assignee, project, dates, etc., check out Issue History for Jira app. It is developed by my team as a customizable…
-
Hi @Porush Verma Maybe you can try the following query: status CHANGED FROM "Re-opened" TO "Closed" Another solution I'd like to suggest is Issue History for Jira (the app from my team. If you need to see changes only for specific status transitions, you can use the status filter. Check if it can help with your case.
-
Yes, you should specify year/month/day. That was only an example.
-
Hi @João Rigueiral Maybe this article will be helpful: https://community.atlassian.com/t5/Marketplace-Apps-Integrations/How-to-delete-an-issue-from-Jira-Save-the-deleted-issues/ba-p/1999805
-
Hi @Sudheer If I understand your request correctly, you need to get a history of changes for the specific user. I'm not good with JQL, so I'd like to suggest the Issue History app for Jira app. Here you can filter issues by assignee, projects, sprints, dates, etc. For instance, it may look like on the screen below: The app…
-
Hi @Diana Paraschiv Have you tried JQL search? I'm not sure, but something like this may work: status WAS Automation Candidate DURING ("2022/06/01","2022/07/01") Another solution you can try is Issue History for Jira (an app developed by my team). Here you can filter by June or any other custom dates. You will see all…
-
Hi @Gnanabaskar Here is the article that can be handy for history searches: https://community.atlassian.com/t5/Marketplace-Apps-Integrations/History-searches-with-amp-without-JQL-10-examples/ba-p/2017596
-
Hi @Yaso Bala Check out Issue History for Jira app. My team has developed it for similar cases you described. Here you can create a report for the list of tickets/issues by adding any standard or custom field as a grid's column. Also, you can filter by sprints, projects, assignees, dates, etc. For example: Export of issues…
-
Hi @Jim Test Account You need to consider a lot of stuff when complying with Part 11 in Jira. In most cases, you'll have to combine built-in functionality with some plugins from the Marketplace. Jira offers an audit log for some system changes: Auditing in Jira Audit log events in Jira For changes within the issues list…
-
Hi @Nalin Dave Sorry if I misunderstood your question, but have you tried to search through JQL like in the example: text ~ "Jira Software" More here:…
-
You can try searching some other plugins for server on the Marketplace. Hope you will find a solution.
-
Hi @Tyler Watts Here is an article about export for different hosting types: How to export issue history from Jira?
-
@Hi @Punit Jain Activity changes are listed in chronological order, not all statuses are in the same line. Have you looked below? Also, you can check the Issue History for Jira app from my team. Here you will find history for the list of issues without the need to open and check each separate ticket. Maybe it helps if you…
-
Hi @Jonathan Hopper The status field is supported by JQL, you can find examples here: * https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-operators/#:~:text=top%20of%20page-,WAS,-The%20%22WAS *…
-
Hi @María López It should be stored. You can lose it if you delete an issue.
-
Hi @Faten.Kutbi You can filter issue history only in some cases: History searches with & without JQL [10 examples] If you're ok with third-party solutions, I can suggest Issue History for Jira. Here you can filter and monitor any standard or custom field. Just add it to the grid's columns and watch the changes. Example…
-
Hi @David Edey What hosting type are you on? There is no built-in option to create an issue history report. You can watch the changes only for a single issue. For Cloud users, I can suggest third-party solutions like Issue History for Jira. Here you can filter issues by project, sprint, date range, etc., and build the…
-
Hi @Daniel Park What data do you need in your report exactly? Most of the historical fields aren't supported by JQL, you can find more info here: History searches with & without JQL [10 examples] If you're ok with third-party solutions, check out Issue History for Jira app. Here you can filter issues by projects, sprints,…
-
Hi @Katherine Stevens You're right built-in ticket history is available only while opening it. If you need to create a report with dates when statuses were changed, you can try Issue History for Jira app. Here you can filter by project, assignees, sprints, date ranges, etc. Add to the grid any field you'd like to monitor…
-
Hi @[deleted] You can try the JQL search, or check Issue History for Jira app. For me, it's simpler as I'm not good with JQL. It's a journal of all users' activities. You can filter by specific assignee and choose a date range if needed. Here is how it looks. The add-on is developed by my team. There is a 30-days free…
-
I see. Sorry, don't know much about automation. Hope you will find a way to solve your case.
-
Issue History add-on itself represents the full issue changelog. You can filter it by project, sprint, assignee, dates, etc., and create the report you need. Export takes a few button clicks. You can get everything without writing APIs here. There is a 30-days free trial, so you can check if it can fit your case. If you…