Mariana_Pryshliak_Saasjet_qysy8m Atlassian Partner

Hello @ben friedman You can try SLA Time and Report, which tracks the SLA status for each task. Regarding your issue, you can set Priority #1 as a Start condition, where 2 and 3 priorities will be a Stop condition. Then Priority 2 configure as Start condition, but 1 and 3 as a Pause condition. This way when the Priority…

Hello @Gabriel Carvajal There are 2 solutions, which can be helpful! Time in status for Jira Cloud generates Status Entrance Date report, which shows the date and time when the issue has entered each of the statuses, and + data points like a key, reporter, status etc, and some additional custom fields. Issue History add-on…

Hello @Gee Udobang If I have understood you properly, you can try to do these few steps. Try to add only those group of people you need to the User Groups and add in the "Browse project" configuration. And you could see only those info you need! I hope it helps. Best regards, Mariana.

Hello @Sudheer Revuru You can find a solution in this discussion:https://community.atlassian.com/t5/Confluence-questions/Team-Calendars-How-can-I-configure-the-calendar-to-have-Sunday/qaq-p/370250 I hope it helps) Mariana

Hello @Luis Zuniga Try Time between Statuses add-on, which generates a report about the time elapsed between statuses (for example, "In Progress" and "Done" statuses) I'm aware there is a time tracking feature, but if it is possible to track the time without user intervention that would be ideal. Everything is shown on the…

Hello @Alexander You can try SLA Time and Report, which allows you to add SLA timer to your Jira issues. As the start and stop conditions, you can select any issue fields. This add-on lets to set SLA goals regarding the time you need. And for overdue issues, there are automated actions(notification, changing assignee,…

Hello @Endre Kallai Jira has its built-in reports, which you can discover here: https://support.atlassian.com/jira-software-cloud/docs/generate-a-report/. If you want to get more detailed info, try add-ons from the Atlassian Marketplace. Such as: Time in Status for Jira Cloud, which generates 7 types of reports: * Time in…

Hello @Mike D There is a similar question in these discussions. So you can try to solve your issue by reading it: https://community.atlassian.com/t5/Jira-questions/Extract-date-and-time-when-status-changed/qaq-p/1229519…

Hello @Petr AST You can try 2 add-ons: Time in Status for Jira Cloud calculates the time in statuses or in status groups. Also, you will have the ability to monitor data in Graphs view and export in the pdf file. Time between Statuses could help to calculate how long did it take in relation to the deadline. And you can…

Hello @Rado You can also try Time in Status for Jira Cloud, which generates 7 types of reports, including Time in Status and Average Time reports. Time in Status report measures how long an issue has been spending in each status. Average time report shows how long it takes an issue to move from "Testing" status to "In…

Hello @Will Davis Tell me, please, which tool do you use for exporting? Did you write on support about this issue?

Hello @Hajnalka Farkas You can try Time in Status for Jira Cloud add-on, which shows how much time an issue has been spending in each status. There are different columns for each status. You don't need any formulas or long configs. In a few clicks, you'll get the necessary data! Also, you'll get data both in Graphs and…

Hello @Vinay Dhuri To check the calculation you can try an alternative solution SLA Time and Report. As Jira Service Desk has flexible conditions for SLA timer, but wе additionally work for Jira core and Jira software issues. You can set whether to calculate only the first cycle or all cycles(including the end one).…

Hello @Nikita K. You can try Issue History add-on by my SaaSJet team, which shows all the changes that have been made to each issue. You'll be able to see the time when a new task has been created or status has been changed. I hope it helps. Best regards, Mariana.

Hello @Jerome Salaun You can try SLA Time and Report, which shows how much time is left to the limit. When the issue is overdue, the minus sign will be displayed on the screen. Also, you can set a few aims, and the escalation level will depend on the aim. I hope it helps) Best regards, Mariana

Hello @Julien_PLATRET You can try Time in Status for Jira Cloud to get the Average time in status report. The info would be represented both in Graphs view and in the Dashboard. If you want to know how long it takes an issue to move from one status to another, try Time between Statuses add-on. It will definitely help. Best…

Hello @Gaurav Malik As an alternative solution to the apps mentioned above, you can try Time in Status for Jira Cloud (calculates the time the issue has been spending in each status) or Time between Statuses (shows how long it takes an issue to move from one status to another). But it will be better when you describe your…

Hello @srinath_17 If your task has been involved in a workflow, you can try Time between statuses (server version). It allows you to set Start and Stop statuses for time calculation. But in case you need the number of tasks in the epic, this tool won't help you. Have a nice day:)

Hello @marina-s If I understood you properly, the same solution has been described in this discussion: https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Calculate-sum-of-values/qaq-p/355398 I hope it helps. Best regards, Mariana

Hello @Vladislav If you want to log your time you can try one of the tools from the Atlassian marketplace. For example, we use ClockWork. In case you want to calculate the time each issue was assigned to any co-worker, you can try Time in Status for Jira Cloud. It generates time in status reports for each assignee or…

Hello @Tomas Løvbukten I did the same a few minutes ago and I didn't notice any problems. This may be a bug.

Hello @Fernanda Grandizoli You can try Time between Statuses (server). This add-on calculates both time in each status and time between statuses. So you can easily solve your issue. To get data about the time in one status you need to choose the same status as "Start" and "Stop" conditions. If you have any additional…

Hello @Sarath You can try to solve your issue with the help of automation and Time between Statuses add-on. This add-on helps to calculate time and notify a particular user if the time is running out. This event (notification of a particular user) may be a trigger in the automation. You can download this add-on on…

Hello @Test User Read this documentation and you could solve your issue easily: https://confluence.atlassian.com/jirakb/how-to-add-customers-without-sending-an-invitation-email-777027023.html I hope it will be helpful Best regards, Mariana

Hello @Prashant Chaurasia As an alternative, you can try Time between Statuses. You should set up a calendar and get ready generated data about Business days in Open status. Just choose an "Open" status as Start\ Stop conditions for a timer and that's all. I hope it helps Best regards, Mariana

Hello @natalie_7 Can you clarify which notification do you need? And you should check the configuration due to the instruction below: https://confluence.atlassian.com/adminjiracloud/configuring-email-notifications-776636790.html I hope it helps Best regards, Mariana

Hello @Gonzalo Fernández Durán As an alternative, you can try a third-party add-on - Issue History. It displays all the changes that have been made in selected issues. You just need to choose a period and get all the necessary data (which changes have been made, by whom and when). I hope it helps Best regards, Mariana

Hello @Victoria I have the same problem, the backlog of the board was not sorted by priority although I used exactly the same filter query: "project = PROJECTNAME ORDER BY priority DESC.It stays unsorted. After deleting the filter, missing the board twice and renewed it also twice I was successful with the following: I…

Hello @Joe Murphy You can try to check the information you are asking for by using Issue History. This add-on will show all the changelog to each issue. So you can monitor who, when and which changes have been made. I hope it will be helpful Best regards, Mariana

Hello @Guy Walker This should be pretty straightforward because you wouldn't care about the agile specific custom fields if you are moving to service desk. If all issue types remain the same it's even simpler, if many issue types end as a single one an many request types, then move per issue type, then each time you move…