Comments
-
you curl statement should look like this: curl -D- -u user:Password X GET -H "Content-Type: application/json" https://jirapro.***.com/rest/api/2/search?jql=labels=Pending&startAt=1&maxResults=2"
-
Hello, All issues, which you can see on a board, are selected by the filter for the board (board settings -> General). Just adjust this filter so that this filter chose issues form all required projects.
-
Hello, If you want to move just a workflow then you can use the export and import workflow. If you want to move more than a workflow then have a look at the Project Configurator plugin or the Configuration Manager plugin. These plugins work only for Server. There are no options for Cloud.
-
The data are stored in the database of the Zephyr vendor for Jira Cloud. For Jira Server the data are stored in AO tables.
-
Hello, You would need an add-on for it. For example, you could use the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview You could create a post function for the required transition with a code like this: 1; counter++persistent number counter…
-
Hello, Next-gen projects do not have releases or release fields.
-
You can read my article here. I developed a webwork there: https://community.atlassian.com/t5/Jira-articles/Part-1-Webwork-with-soy-requirejs-backbone-js-in-Jira-plugins/ba-p/828459
-
Are you sure that you did not forget the NOT before the status word? This JQL query will show you all tickets which were NOT moved from the In Development status and right now the status is In Development
-
Hello, I think your JQL query should be like this: not status changed from "In Development" after -14d AND status = "In Development"
-
Hello, It is a webwork: https://developer.atlassian.com/server/jira/platform/webwork/
-
Hello, Before migration of next-gen projects to classic projects export all issues to a csv file (go to Issue navigator, enter project = yournextgenproject and export to csv all fields). Then after converting to a classic project, you can create new fields in Jira (Issue -> Custom Fields) and set to these new field values…
-
Hello, Have a look at the filter, which is used by your board (board settings -> general). Then execute the search rest point with ?jql=filter=yourfilter. https://docs.atlassian.com/software/jira/docs/api/REST/7.12.0/#api/2/search-search You will get all required issues.
-
Hello, You can not assign a ticket to a tempo team. Tickets can be only assigned to users.
-
Hello, Kindly make sure that the Watcher role is linked to the Issue Update event in the project configuration scheme.
-
Hello, You need to give more details on what you want. Projects do not have start time and end time. Maybe you use an add-on. If so, you should mention the name of the add-on.
-
I think it is possible though I do not have a script.
-
Private filters will not be in the list.
-
Hello, If you want to get all filters (even filters, which are not shared with you and private filters), you need to execute sql to your database: SELECT s.filtername, s.authorname, s.DESCRIPTION FROM searchrequest s
-
You are most welcome! If my answer helped you, kindly accept my answer.
-
On Server you can not import a csv file via the Issue Navigator. You must be a Jira administrator and import it via System -> External System Import.
-
Hello, Only Jira System Administrators can install add-on. Make sure that you are a System Jira Administrator in System -> Global permissions
-
Go to System -> External System Import. Then choose CSV.
-
Hello, You can import issues to Jira in the csv format. You can find more info here: https://confluence.atlassian.com/adminjiracloud/importing-data-from-csv-776636762.html
-
Hello, What do you mean by linking? Issues are selected by filters for boards. That is why if you want an issue to appear on a board, you should change the filter for this board accordingly. If you want to link issues, then use the standard linking feature:…
-
Hello, a Sprint does not belong to a board. If two boards select the same issues and you include this issue in a sprint in one board, this print will be visible on another board. If you rename this sprint in one board, the sprint will be renamed in the other board. If you close this sprint in one board, this sprint will be…
-
Hello, You would need an add-on for it. For example, you could use the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview You could write a post function with a code like this: #{Your custom field name} = #{Your custom field name} + 1;
-
Hello, You would need an add-on for it. For example, you could use the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview With this add-on you could create a job, which is run by schedule. In this job you would select all issues with expired…
-
Hello, Go to the Issue Navigator and run the following JQL: project = yournextgenproject Then export results to a csv file.
-
The link, which is provided, can be installed via the upgrade procedure. After it your Jira software application will disappear.
-
Hello, A version is linked only to one project. If you want multi project releases, you would need an add-on like Portfolio.