Natalia_Kovalchuk_SaaSJet_ Community Champion

Hi スズキ! In case you would be open to considering other apps for export, you might take a look at Issue History for Jira (Work Item History) from SaaSJet as an alternative solution. It allows you to generate structured Excel reports that include the full work item history (including custom field changes, status transitions,…

Hi, Farma Fusion! In Jira, comments can't always be included in standard CSV exports. It is especially true if you are using the default Jira export. This may appear to be a system limitation, but it often depends on the export method and the fields selected. To include comments in the export using Jira native…

Hi, Isha Gupta! Such an error can appear when Jira has problems with processing one or more fields during export. The most common reasons for that include selecting too many work items, fields with unsupported formats (e.g., rich text, complex custom fields, marketplace app fields), and permission restrictions. You can try…

Hi @G P N! You are right, JQL can't query historical values of a field, only the current value. If you are open to third-party apps, I recommend the Issue History for Jira (Work Item History) app by SaaSJet. It is supported on Jira Data Center and allows the generation and export of reports covering the full history of…

Hi Natalia! In your case, I can propose that you try the next options: 1. Create a JQL filter like project = X AND created >= startOfMonth() 2. Try to use a dashboard gadget (like Created vs Resolved Chart). 3. Try Issue History for Jira (Work Item History) from SaaSJet team. This app allows you to track how many tickets…

Hi @jyoti_suryan ! When a sprint starts, Jira may automatically apply internal board logic. If board columns allow only specific statuses, Jira can adjust task and sub-task statuses to match them. Jira can also sync subtask statuses with the parent task at the start of the sprint. These changes can be done by the system…

Hi @Veena Kunchala ! Unfortunately, Jira doesn't store the original description format (tables, headings, rich text) in work item history. There is no built-in way to recover the original formatting from history logs. You can try using Marketplace apps, such as Issue History for Jira (Work Item History) from the SaaSJet…

Hi @Olga Mello ! Unfortunately, Jira doesn’t offer a one-click export of the entire space's data into a single Excel file for offline backup. On the free Jira plan, you can export work items only via filters → CSV. If you are considering using a third-party app, I recommend the Issue History for Jira app from the SaaSJet…

Hi @Giulio Pengo! Jira’s native CSV exports are very basic and are not Excel-friendly. If you need to export a list of Jira tasks on a regular basis and can consider the option of using third-party apps, I can recommend you try Issue History for Jira app provided by SaaSJet team. The app lets you generate analysis-ready…

Hi @reforres! Unfortunately, the built-in Jira gadgets usually don't support exporting to Excel. If you need to export activity or work item changes in Excel format, you can use the Activities gadget in the Issue History for Jira app (SaaSJet). It clearly shows who changed what and when. You can filter the data by project,…

Hi, @hhasan! This could happen because of how Jira exports comments. I suppose Jira doesn’t always export the full comment text and instead shows hyphens as placeholders. It’s especially common with longer or formatted comments, which Jira’s CSV/Excel export doesn’t handle very well. In such cases, I recommend using Issue…

Hi @Flester Iulian , If you need to get the complete work item history for audits and analytics, meaning what was changed, when, and who is responsible for it (including comment changes and deleted work items), then building this fully on your own with Jira APIs becomes a lot of heavy engineering and ongoing maintenance.…

Hi @NEGAR JALALIAN , I can recommend you try Security Scanner View (PII & DLP) provided by Issue History for Jira app (SaaSJet). It can automatically scan your Jira work items and their complete change history for sensitive data. It includes passwords, credit card numbers, social security numbers, API keys, IP addresses,…

Hi @Bob Scudder , welcome 👋 You can try gadgets for Jira dashboards (no SQL or programming required). For example: Filter Results gadget - shows the list of tasks based on a saved filter, helping you quickly see and monitor the work that matters most. Pie Chart gadget - allows seeing the distribution of tasks by status,…

Hi Nikola Vojtek! AI-based scanning is a part of our long-term plans. However, at the moment, implementing AI is limited by the current Atlassian platform constraints. As soon as Atlassian enables the necessary capabilities, this is something we fully intend to implement. For now, our scanner is pattern-based, which is…

Hi Nikola Vojtek! Thanks for your interest in our Security Scanner and your question. Right now, our Security Scanner View (PII & DLP) automatically scans Jira work items to detect sensitive data using common and well-known patterns associated with sensitive information. This includes: * Password / passphrase * Login…

Hi @Suraj Pawar! Can recommend such tools for tracking your team activity and progress in Jira: * Activity Section (on each work item) - displays updates, comments, and a detailed history of all work items. * Created vs. Resolved Issues report - can help you monitor the team's workload and progress over time. * Activity…

Hi @Bittu Kumar ! In case the time was logged via Tempo, Jira saves the worklog as created by the Tempo app user, not the real person. The real name of the author and the original comment are stored inside Tempo, not in Jira. That is the problem. So when you call: GET /rest/api/3/issue/{issueIdOrKey}/worklog Jira can only…

Hi @Raheem Pillay ! If you need better reporting in JSM, I recommend the Activities gadget from Issue History for Jira (from SaaSJet team). It's a simple and practical option. It shows a live activity stream of what actually happens in requests. For example: status changes, field updates, assignee changes, and custom…

Hi @Deepali Dabholkar ! In your case, I want to recommend you try the Issue History for Jira app from my team. With it, you can easily export your epics, including a detailed history of their updates, from Jira to Excel. For that, you need to do the following: 1. After the app installation from Atlassian Marketplace, open…

Hi @Jader Peixoto Volkmer ! You can use JQL to check what tickets ever passed through a specific status. For example: It allows you to retrieve a list of tasks that were in the Reopened status (or, in your case, in Reproved by QA status), regardless of their current status. Also, if you’re considering third-party apps, I…

Hi @Seamus Largey ! If you are considering third-party apps for export, I can recommend Issue History for Jira from my team. It exports to Excel without formatting loss and keeps descriptions in a readable, single-line format. It also includes full change history, comments, and other useful reporting options. Also, you can…

@MichaelThai, maybe you can try using Epics for Features? 

Hi @MichaelThai! I can propose a simple way to manage multiple brands in a single Jira board: tag each task with a label representing the brand. For example, you can add labels such as Brand-A, Brand-B, and Brand-C. Once labels are added, you can instantly get the status and progress of any tasks related to a specific…

Hi @Pratik Acharya ! Here are some Jira built-in features and tools for tracking team activities: 1. Created vs. Resolved Issues report - helps to monitor the team's workload and progress over time. 2. Activity Stream gadget - allows you to see the latest updates, comments, and transitions between the chosen projects or…

Hi @Karen Furnell! There are a few possible options for keeping a copy of your Jira Cloud data. Here are some of them: * export project data through Jira Cloud site backup (XML format): However, Jira's XML backup doesn't include the full work item change history in a readable format. * use Jira's built-in functionality and…

Hi david gue! The data you see in the Activity section comes from the issue’s changelog. To get this history using the REST API, you can use: GET <span>/rest/api/3/issue/{issueIdOrKey}/changelog</span> This request will help you get the full changelog for the issue (who changed what and when). If you ever need an easier…

Hi @ckopanon ! It isn't possible to do this directly with JQL, as it doesn't support calculations between two date fields, such as created and resolved. However, you can try these workarounds: * Created vs Resolved Chart - shows the number of tasks created and resolved during the specified time period in a project. * Issue…

Hi @Shaik Asif Ali ! To export the JSM project field data, you can use such options: * Go to Filters →All work items → Advanced Search (JQL). Use a query like: project = PS (in this case, it's a People Support project from JSM). Then, click Export and choose CSV (all fields). You'll get a file with all visible fields and…

Hi @Nihar Sharma! Jira does not have an easy way to view all users involved in a particular project and the activities they have performed. It is possible to use JQL to get the part of the info you need, for example: 1. project = DEVS and reporter IS NOT EMPTY - it shows all work items with reporters in the project.…