Mehmet A _Bloompeak_ Atlassian Partner

Hi @Alicia Redden Welcome to the Atlassian Community! "Days in progress" data is available in issue history and you can get it using Jira Rest API. It provides status changes for each issue by returning a json which you need to parse to calculate the time passed in "In Progress" status. If you prefer using a marketplace…

Hi @Celina Kim As far as I know, you cannot exclude weekends in JQL. You can use a third party app to exclude weekends. If you prefer using a marketplace app, you can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status and status durations…

Hi @Vera Valshonok The raw data you need is available in issue history and you can get it using Jira Rest API. It provides status changes for each issue by returning a json which you need to parse to get status transition time. If you prefer using a marketplace app, you can try Status Time Reports app developed by our…

Hi @Dionne Hairsine, I guess, you are referring to our Status Time Reports Free - Time in Status app. Regardless of the calendar selected, while displaying the duration, our app takes 1 day as 24 hours. Therefore, "1day 15 hours" is "39 hours" and this duration is the time passed in the working hours. That is, it does not…

Hi @Petru Simion _Simitech Ltd__, I agree with you, each project can have different workflow and apps cannot calculate cycle time and lead time without knowing which statuses should be included in calculation. You can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how…

Hi @Vera Valshonok, As far as I understand, what you are looking for is a lead time (the time interval between the moment an issue is requested to the moment it is completed) report. The raw data you need is available in issue history and you can get it using Jira Rest API. It provides status changes for each issue by…

Hi @Nico Both issues are still in In Progress status. Therefore our second automation rule did not execute yet. Once you transition them to next status in your workflow 2nd automation rule will execute and will create worklog. The comment on the 2nd issue is created 4 days ago by your initial automation rule you mentioned…

Hi @Nico , The second automation calculates the time passed in "In Progress" status, but it does not store it in a custom field. Instead it directly creates a work log using the calculated time. That was your initial requirement. If you also want to see the calculated time in a field then * Create Number type custom field…

For no.2, you need a custom field and 2 automation rules. * Create a custom field named In Progress Start Time Choose the Date Time Picker field type. Our automation will use this field to store the time when the issue is transitioned to "In Progress" status. * In the first automation: * Rule name: Store time issue enters…

Hi @Nico , Could you please clarify your request a little bit more? Are your looking for to * get the time passed since the issue created till the issue is transitioned to "In Progress" status * or get the time passed while the issue stayed in "In Progress" status and then automatically log work using this value.

Hi @Vera Valshonok As far as I understand, what you are looking for is a cycle time (the time it takes for the team to start working on an issue and complete it) report. The raw data you need is available in issue history and you can get it using Jira Rest API. It provides status changes for each issue by returning a json…

Hi @Ken Rupin As far as I understand, what you are looking for is a cycle time (the time it takes for the team to start working on an issue and complete it) report. The raw data you need is available in issue history and you can get it using Jira Rest API. It provides status changes for each issue by returning a json which…

Hi @Lubna Malik , There are below solutions. The raw data you need is available in issue history and you can get it using Jira Rest API. It provides the status changes for each issue. It returns json, then you need to calculate status change count by coding which parses issue history rest api json for each issue. You can…

Hi @Rémy Hilbert , There are 2 alternatives to Control chart. The raw data you need is available in issue history and you can get it using Jira Rest API. It provides the status changes for each issue. It returns json, then you need to calculate cycle time by coding which parses issue history rest api json for each issue.…

Unfortunately I do not have any other idea.

Hi @Brent Lee , Could you please share screenshot from the SLA's edit page? By default SLA finish condition might be "Resolution:Set". That is, when the resolution field of the issue is set then SLA finishes. And your status change might not be triggering the resolution to be set. As a workaround you can add "Status…

Hi @ethan , As others mentioned it is not possible to have custom ordering in two dimensional filter statistics gadget. On the other hand if you consider using marketplace app, you can try Reports - Charts and Graphs for Jira app developed by our team. In this app, you can order the results by drag&drop without the need to…

Hi @Mar , We developed Status Time Reports app for this exact need. It is free up to 10 users. If you are looking for a completely free solution, you can try the limited version Status Time Free. If you have any questions, feel free to schedule a free call with us.

Hi @shiva kumar Gosul , Your approach is helpful for detecting issues assigned to inactive users. In your terminology inactive users are the ones that do not have access to Jira anymore. They were deactivated by the Jira admin via user management page. I guess what @Mahesh Kumar is asking different. He is looking for a way…

This is because your project is team-managed and my project is company-managed. Team-managed project board UI is different. You can find your filter by using the below url. /jira/software/c/projects/YOUR-PROJECT-KEY/boards/YOUR-BOARD-ID/?config=filter Please replace YOUR-PROJECT-KEY and YOUR-BOARD-ID with your actual…

I guess it returns the organizations ordered by their ids. The ids are generated by the organization creation date. It is not possible to get organizations ordered by name. You need to get all the organization page by page and then combine them into a single json array. Then you can sort it using javascript coding.

Hi @Annika Åström , You can have multiple projects in a single board by editing the board filter. * Click on the 3 dots in your board * Click on Configure board * Edit your filter query to include multiple project. e.g project in (Project-1, Project-2)

Hi @Ruchi , As far as I know the only option is using rest api and it returns JSON not CSV. https://developer.atlassian.com/cloud/jira/service-desk/rest/api-group-organization/#api-rest-servicedeskapi-organization-get The rest api has pagination, it takes 50 organization on each page. You need to modify the start parameter…

Hi @Mar , It is not directly possible in Jira. As a solution you can use Jira automation or a marketplace app. You can check the below article for Jira automation: https://confluence.atlassian.com/jirakb/automation-to-sum-up-story-points-of-stories-in-different-statuses-and-add-the-value-to-the-parent-1108673757.html If…

I guess patch type is a custom field. You can try the built-in "Issue Statistics" gadget. It will display results in a table view not as in your attachment. But it can show number of issues by patch type. You need to * combine the 3 filters into a single filter and use this filter. * set Statistic Type=patch type If you…

Hi @Suma Kustagi , What are the values in your attached gadget? Are they story points in each sprint?

Hi @Mahesh Kumar , There is no direct way of doing this in Jira. The solution provided by @shiva kumar Gosul lists the issues and then you can check the assignee columns to see the inactive users. However, it will not show the inactive users who are not assigned to any issue. You need to fetch all users via below rest api…

Hi @Vandango As a workaround you can delete all the cookies of community.atlassian.com. After you opened https://community.atlassian.com in your Chrome you can apply the below steps. If you still have the same problem. You can delete the cookies of https://id.atlassian.com and try again.

Hi @Dick , You can use the below rest api: /rest/api/3/user/permission/search?permissions=CREATE_ISSUES&projectKey=YOUR-PROJECT-KEY

Hi @jovanio_junior By default, Jira does not track deleted issues and deleted issues are lost forever. To prevent it happening again, you can try Restore Deleted Issues app developed by our team. In order for this app to work, the app must have been installed before the issue is deleted. After you install this app, * Both…