Yuliia_Borivets_[SaaSJet] Atlassian Partner

Hi @Kaitlin Madsen If you're interested in issues added after the sprint is started, maybe the Sprint Burndown chart can help. It shows all the issues added/removed during the sprint. The date is available. Also, there is the scope change log in the table view. It helps me sometimes. Have you tried it?

Hi @Aaron TP If you'd like to filter the issue history and customize your report, check out the Issue History app. Here you can filter by project, sprint, assignee, etc., and choose any date range. Add any custom field to the grid columns to manipulate output data. Check it out if you're ok with third-party solutions. The…

Hi @Guy LaRochelle Plusing to Bill's answer, here is the post that might be helpful with REST API or add-ons: How to export issue history from Jira?

Hi @Dalia You can try to export ticket history via API or other solutions for different hosting types: How to export issue history from Jira? After that, you can make the report and analysis you need. If you're on Cloud, check out the Issue History add-on. Here you can customize your report and add any standard or custom…

Hi @Foxcliffe Hickory What is the exact data you need to see in the sprint report? I can suggest checking the Issue History plugin if you're ok with it. Here you can filter issues by project, sprint, etc., and choose the date range you need. The add-on is developed by my team as a journal for every past activity. Let me…

I'm glad to help :)

Hi @Ine Nieuwenhuijzen You can find who has created the ticket in the History section. Open an issue (ticket) > Activity > History In case, you need a more advanced report, I can suggest the Issue History plugin. Here you'll get info for the list of tickets and the ability to sort them according to your needs. My team…

@Taranjeet Singh Glad to help!

Hi @Taranjeet Singh Cycle time is the time from the beginning to the end of a certain action. It is the time during which the issue is marked as "In progress". The statuses used to calculate cycle time depend on the workflow you're using for your project. Lead time covers a longer period of time: from receiving a request…

Hi @Matt Melvin If you're on Cloud, check out the Issue History for Jira app from my team. It might be helpful in case you'd like to track a history of status changes for some date range. Here you can: * Filter issues by project, sprint, assignee, etc. * Set any given or custom period * Add any standard or custom field as…

Hi @Haitham M.Kamal Another solution you can check out is the Issue History app (if you're on Cloud). My team has launched the Keep deleted issues option to track who has deleted a ticket and when.

Hi @Pramod gautam You can find some ways in the article below: How to export issue history from Jira? If you're on Cloud, check out Issue History for Jira. The app is developed by my team as a journal for every update. Here you can download history as XLSX or CSV files.

Hi @Divyajyoti Sarangi I'm not aware of all the requirements for SOC 2 and ISO certification, maybe there is some app on the marketplace. For system changes, you can check Jira audit log: For an internal audit of the teamwork, I can suggest the Issue History add-on from my team. It provides you with a report for every past…

Hi @Mitra Nami I'm not good with coding and API, so I'd like to propose an alternative solution from my team. If you're on the cloud, check out the Issue History for Jira app. Here you can easily filter by Project, Assignee, Sprint, and choose any date range you need. As result, you've got a changelog for the list of…

Hi @Zainab Arooj I would like to suggest a solution from my team. Maybe it will be helpful for someone. With the Issue History add-on you can filter the history of changes by Assignee (and other options: Project, Reporter, Sprint, etc.) and select any dates. 

Hi @Lisa Besteni Story points are helpful if you need to estimate the number of different factors: * the difficulty of the job * the volume of work * experience completing similar tasks * possible risks or uncertainties, etc. SPs are flexible and relative. It takes some time to get used to the estimation. Within our team,…

Hi @Suma Pralhad Kustagi Here is the article for different hosting types: How to export issue history from Jira?

Hi @Aditya Another solution you can check out is the Issue History add-on developed by my team. Here you can arrange the columns and add fields (assignee, time spent) you need to the report. Also, you can filter by project, sprint, date range, etc. Export to CSV and Excel is available.

Hi @Charu Singhal This JQL should work for you: assignee changed ON '2022-02-07' Another option I can suggest is the Issue History app developed by my team. Here you can filter by assignee, project, sprint, etc., and choose the date range you need. Let me know if you have any questions.

Hi @Lize Gersbach There are some solutions I'd like to suggest: 1. You can see when an item is moved from state to state with the history option in the activity section. To make a report you can try to export the data via REST API. 2. With the Issue History for Jira plugin you can add any field to the grid and get the…

Hi @Daria Pavlova Maybe these materials will be helpful: API: Workflow statuses How to export issue history from Jira?

Hi @douglas_cordeiro 1. Yes, it's possible with the history option in the activity section. It shows what updates are made, by which user and when. 2. If you need to detect all changes for the list of issues for some project, sprint, assignee, etc., you can try Issue History for Jira app. My team has developed it as a…

You can find out about new or deactivated users in the Jira audit log. Here is the topic-related article: Audit in Jira: How to get Jira audit log and issues changelog?

Hi @Matt Hyne Here is an article about exporting activity history with REST API and plugins: How to export issue history from Jira? If you need to export the audit trail, you can try the Issue History for Jira app. My team has developed as a journal for every past activity. Here you can filter by date range and choose any…

Hi @Sidhant Sharma You can try the following solutions: 1. The simplest way to look for assignee changes is ticket history in the activity section. It looks like that: Solutions from the Marketplace developed by my team: 2. Issue History – journal for every past company's activity, including assignee changes. 3. Time in…

Hi @Sayed Kamaloddin Peerzade If you're comfortable with solutions from the Marketplace, I can suggest 2 developed by my team. 1. Issue History – journal for every past activity, including status changes. Here you can filter by assignee, reporter, project, date range, etc. 2. Time in Status for Jira Cloud will be even…

At the single issue level, you can look for history in the Activity section. It has data on sprint movements. If you'd like to get a broad picture of a list of issues for some project, sprint, assignee, try the Issue History app. My team developed it as a journal for all updates. You can also export issue history for…

Hi @b_hassan21 Yes, you can see data for closed sprints. Every issue update will be fixed. For example: who has moved the issue from in progress to done. You can filter by sprints or date range and add any columns you need as created or resolved. Also, export is available, so you can analyze data further.

Hi @Alejandra González 1. You can open the history option for each ticket. You'll find it in the Activity section. There is available info about assignee changes. 2. If you need a more extensive view (for list of tickets), you can check Issue History for Jira. My team has developed this plugin as a journal for every past…

Hi @John Scott For your issue, it will be helpful to find a lead time. Check out the following article: 3 tools to analyze Cycle and Lead Time in the Jira I can suggest trying the Time in Status for Jira Cloud add-on developed by my SaaSJet team. Get all Jira time spent reports in One Place Monitor the team performance and…