Yuliia_Borivets_[SaaSJet] Atlassian Partner

Jira is known for its agile and customizable possibilities. But, yes, you should check if it fits your case. I wish you find the best solution for your company.

Hi @Elif Avsar In general, it's possible. I know some companies use Jira to comply with Part 11 FDA. But built-in functionality usually isn't enough. You will need to combine it 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…

Hi @Amirhossein fathollahi madani If you're comfortable with using solutions from the Marketplace, there is one I'd like to suggest from my team. Consider Issue History add-on. It shows all the updates made to the selected issue list. So you will see issues, their assignees, sprints and any other column. You can filter by…

Hi @Alejandra González There is no built-in option to download ticket history in Jira. If you feel comfortable with it, check out solutions from the Marketplace. One of them is developed by my team. With Issue History add-on you can export ticket history as CSV or Excel file. All ticket updates will be presented in the…

Hi @David Stokes Jira issue history shows if a ticket was moved from the sprint to backlog only at the issue level. There is the Issue History add-on where you can get a list of tickets that were updated. You will see all the changes including sprint details in the grid. It will look like on the screen below. My team has…

Hi @kotha Eswar rao This is a paid plugin, but there is a free trial version for one month. So you can test if it will be helpful for you. You will see the date till which it's free after the installation. Regards

Hi @kotha Eswar rao If you're comfortable with another solution rather then JQL, there is an add-on from the Marketplace. It's Issue History and it's pretty simple to use. You can look back for ticket history in table format and quickly find out if there were any comments added. Just choose 48 hours or dates you need from…

Hi @Santiago Pedrosa Pérez Not sure, but you can check audit log. It should record some activities for security and logins. I've never tried cause I don't have the Administer Jira global permission. You can read more here: Audit log events in Jira Audit activities in Jira applications

Hi @Reid Bourgeois Unfortunately, JQL can't be implemented in this case. If you're comfortable with solutions from the Marketplace, check out Time in Status for Jira Cloud app developed by my team. You can get the date when an issue moved into a particular status with the Status Entrance Date report. It looks like this:…

Hi @Vadym Kalujny If you need to find out how long an issue has spent in each status, consider also Time in Status for Jira Cloud. My team has developed the add-on to calculate time in status without time tracking. Sometimes it's difficult to organize a team to log working hours. With status duration reports, you’ll be…

Hi @Bret Justus Maybe this article with cycle/lead time will be helpful in this case: 3 tools to analyze Cycle and Lead Time in the Jira Also, if you need to calculate time for some statuses, excluding others (“Awaiting on Dependency” in your case), check out Time in Status for Jira Cloud. You can create status groups to…

Hi @David Loszewski Thanks for your question. Currently, there is no such option. I will inform our product development. If you use our app, you can add a feature request in the add-on menu.

Hi @Tatiana Viana As it was said in the previous comments, built-in functionality doesn't support storing history for the deleted cards. You may search Marketplace solutions to get what you need. If you're comfortable with it, you can try the Issue History add-on developed by my team. There is an option to keep deleted…

Hi @Laura Ramirez There are several options you may check out if you'd like to know when a story has changed its status. 1. Look for issue history as it was suggested before. You will find it in the Activity section while opening each issue you're interested in. 2. Look for solutions from the Marketplace. You might…

Hi @Yatish Madhav If you're interested in changes for issue fields (Key, Summary, Status, Priority, etc), you can check issue history in the Activity section while opening each issue you're interested in. To get change history for the list of issues, you can try the Issue History plugin (developed by my team). There you…

Hi @Caio Vinicius de Queiroz Luz If you'd like to export issue history for a list of issues, you can try the Issue History add-on. It provides a ticket history report of all changes that have been made in the selected list of issues. There is an option for export here. The app is developed by my team, so let me know if you…

Hi @David Loszewski You can look for history in the Activity section while opening each issue you're interested in. If you'd like to see a general list with all issues for some project or assignee, you can check solutions from the Marketplace. My team has developed the Issue History add-on for this aim. It provides a…

Hi @Daria Pavlova If you need to set SLA for non-Service Desk projects, you can use third-party add-ons. SLA Time and Report app can help if you are on Cloud (it's developed by my team). It works for Jira Software, Jira Core, and Service Management. Also, you can use it for Classic and Next-gen Projects. Kind regards

Hi @Danny Bish If you are on the cloud version, you can check out Issue History add-on. My team has developed an app to monitor all changes that have been made in the selected list of issues. It helps to find out what changes were made, by which user, and the date when modifications occurred. You can filter by sprint,…

Hi @Madison Byers Maybe this article will be helpful for you: How to earn badges on the Atlassian Community Besides, you can check the badges section of your profile. There should be a link on some badges to an article that explains what you need to do to earn it. Kind regards

Hi @Emily Zhou You aren't the only one who had to deal with this issue. It occurs, and we all need a place to keep our data from being lost forever. My team has developed the Keep deleted issues feature for the Issue History add-on. So, it's possible to start storing every issue you delete after activating the feature. It…

Hi @bela shaji You can try other solutions. * Filter issues that were not completed in the previous sprint with JQL like this: project = MYPROJECT AND NOT status = Done AND Sprint = NN * Look for incomplete issues in the Sprint burndown chart. But as not all of the incomplete issues might go to the next sprint, these two…

Hi @Curt Baker Another solution you can try to find out who has moved a ticket is the Issue History add-on. You'll get an issues list with all changes, including a person who has updated a ticket and when it was updated. Selecting date range is also available. Hope you'll find this info helpful. This app was developed by…

Hi @albert_pinto If you're still looking for a solution, you can check out SLA Time and Report. It allows setting SLA time goals not only for JSM tickets but also for Jira issues. So you can set SLA for L1, L2, L3, L4 teams. To create SLA measurement you will need to: * Choose Start/Stop/Pause conditions from standard and…

Hi @FUJIMOTO If you need to get transition history you can also check out Issue History add-on. You'll get a history journal for every activity and find out: * What changes were made to the issues * The date when modifications occurred * Which user has made the changes For further analyzing you can export it to a…

Hi @James Wardle If you're still looking for a solution, check out Time Between Statuses. My team has developed this app to monitor the execution time between statuses in the workflow (e.g. from "in progress" to "done"). Here you can set time limits to highlight overdue issues. You can schedule working days, time…

Hi @Chris Hickey My team has developed an Issue History app to monitor all changes that have been made in the selected list of issues. It's a history journal for every activity which help to find out: * What changes were made to the issues * The date when modifications occurred * Which user has made the changes

Hi @caof To get the time that an issue spent in each status, consider these options: * Built-in Jira feature Days in Column (available only for classic boards). You’ll get only the number of days an issue has stayed in the column. You can learn how to enable this feature here. But if you instead need to remember time…

Hi @Shannon S Thank you for reminding the rules. I believe I try my best to follow them, Anyway, I will not respond to 6 months older questions.

Hi @mhenderson In case you need to find out when an issue has moved from one status to another, you can check Time between statuses by SaaSJet. The add-on tracks transition time between statuses (e.g. from "in progress" to "done"). It also helps to set such calculation conditions as first/last transition and to/from…