Mehmet A _Bloompeak_ Atlassian Partner

Hi İlknur, Next-gen projects are isolated, they do not share fields with other projects. Therefore you end up with multiple fields(in your case statuses) with the same name. There is the request JRACLOUD-74037 to fix it. You can vote for it. But at this point in time, the only solution is to not use next-gen projects.

Hi @Grupo Espirita Casa do Caminho , It seems you found a bug on Jira. You can create a bug to Atlassian Support. https://support.atlassian.com/contact

Version number can be retrieved via below rest api. https://ecosystem.atlassian.net/rest/api/3/serverInfo

Hi @Julien_PLATRET , As an alternative you can try Status Time app. It displays average status time. You can check the online demo and see it in action. If you are looking for a free solution, you can check Status Time Free. It is limited bu free version of the above. Hope it helps.

Hi @Nicolau Rodrigues , In your final url, expand is part of jql. Instead it must be a request query parameter as below. https://mycompanyjira.atlassian.net/rest/api/2/search?jql=project%3PROJECTKEY&startAt=0&expand=changelog

Hi @Gaurav Malik , If you are looking for status entry dates for a bunch of issues, you have to look for each issue history one by one. If so, you can search for a marketplace apps which provides report for status entry dates. We developed Status Time app for this exact need. Apart from time spent on each status, it…

Hi @Helen Snowball , I couldn't visualize "group by status" and "order by priority" together. When you group by status you will end up with a table similar to the below |Status | Issue Count | |ToDo | 30 | |InProgress| 12 | |Done | 10 | You can not order the above table by priority. Maybe what you are looking for is "group…

Hi @Aviad Hadida , We have a similar workflow. It is not a direct answer to your question but it can give you an idea. Below is how we do it. ReadyForDevelopment -> InDevelopment -> ReadyForTesting -> InTesting -> AcceptedInTesting We estimate the complexity of the story as story points. The estimate includes both Dev and…

Hi @steven cheng , You can create a custom field(with name 'developed by' or 'team members') of type multi-user picker and add all members who will work on the story.

If the org admin has company email address, you can recover the password by getting access to the mailbox, otherwise there is not way.

Hi @Nawoda Herath , As an alternative solution, you can create a custom field named 'developed by' and use this field in your report.

Hi @Jerome Salaun , Apart from standard gadgets you can check Status Time app developed by our team. One of the reports it provides is average status time. It also takes into account your working hours. That is, once you define your working hours and holidays into the app, then cycle time for a support ticket created on…

Hi @Decho Iliev , Query parameter works with exact matching. So it is not possible. You can get all projects using /rest/api/3/project/search . It returns an array of projects. So you need to filter the result by key starting with TEST.

Hi @Juliane_O , For Jira, it is available via rest api. Server: https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/#api/2/applicationrole Cloud: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-application-roles/

Hi @Shane Wilson , It is possible with git hooks. Search google for "git pre-commit hook jira id" and hope you will find sample scripts.

Hi @afsal nazar , As far as I know it is not possible with standard features of Jira. You can use marketplace apps. Our team developed Status Time app for this exact need. It provides average report with grouping on any field. e.g, average in progress time by issue creation week or average cycle time by project. The time…

Hi @Alison Whittaker , You can create a custom field named participants of type user picker(multiple users) and associate the field to your epics and tasks.

Hi @Ganesh muralidharan , If you distinguish between test case creation and execution steps via Statuses or any other custom select field, then Status Time app will solve your problem. It displays time spent on each status/custom select field based on your working calendar. You define your working hours and holidays in the…

Hi @Mark Sliwinski , I guess you are calling AP.request using an app. The app must have WRITE scope to be able to create an issue. See the scope documentation for the details. https://developer.atlassian.com/cloud/jira/platform/scopes/

Hi @Luiz Felipe Ferreira , Apart from Jira standard reports, you can check Status Time app. It provides time spent on each status based on your working calendar. You define your working schedule into the app. Then, if the issue is opened on Friday at 5 PM and closed on Monday at 9 AM, cycle time based on your working hours…

Hi @Vladimir Razumeyko , With automation, the time logged ignores your breaks and weekends. Our team developed Status Time app, which calculates time spent on each status based on your custom working calendar and holidays. Then you can get a report on actual working time for each status. You can check the online demo and…

Hi @Rohan Nishantha , You can list all the filters using filter rest api and then search for your field name in the response. https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-filters/#api-rest-api-3-filter-search-get

Hi @xdev , Are you using git? If so, you can revert commits via command line * List the commit ids withgit log * Revert the commit by idgit revert {commit Id}

Hi @Sam Sa , Unfortunately, It is not possible using standard features of Jira. But it is possible with third-party apps in the marketplace. https://marketplace.atlassian.com/addons/app/jira

Hi @lee , There is no built-in solution in Jira. You can use Jira rest api to extract all issues, parse the json output and group them by creation hour. We developed Status Time app. Its main functionality is to provide time passed on each statuses but it has the functionality to group issues by creation hour. It does not…

Hi @amcgurty , You can see the version using rest api. E.g. https://ecosystem.atlassian.net/rest/api/3/serverInfo

Hi @Pablo Castillo , If it is a custom field, I suggest you to check the type of that custom field. You need Jira admin rights to see the details of a custom field and below is the url listing all custom fields. https://[mydomain].atlassian.net/secure/admin/ViewCustomFields.jspa

Hi @Asha , I guess Atlassian restricted the export of user names due to GDPR. But in my opinion, it is meaningless not allowing exporting user names that I am already allowed to see inside the web page. The only way seems to use below Jira rest api. You should parse the json api response, create user ID --> user name…

Hi @Vijayalaxmi , See the online demo of Status Time app on how it calculates status time for each story. It has the export functionality too. You can play with and see it in action. If you are looking for a free solution, you can check Status Time Free. It is limited but free version of Status Time app.

Hi @Aliaksandr Maletski , It is a known behavior or a problem depending how you see it. There is the open ticket waiting for Atlassian to solve. You can vote on it. https://jira.atlassian.com/browse/JRACLOUD-61841