Comments
-
Hey @Adam Wordsworth Could you share the an example of the payload that triggered the issue on the endpoint you've shared and the payload that fixed it?
-
Hey @Mark Van Loock As of May 9th 2024 the products field has become mandatory when creating users (see changelog and the deprecation notice for more information). Valid product name for the products field: jira-core, jira-servicedesk, jira-product-discovery and jira-software. To create a user without product access, set…
-
Hey @ヴァリエンテ フロリアン_Florian Valiente_ sorry for the delay, glad you were able to resolve the issue!
-
Hey @nicole liliana bassi The HTTP 415 error is likely the result of a missing Content Type header. Since the endpoint requires the organization id to be passed as part of the request payload, the Content Type header has to be passed. When this is not done, or an incorrect header is sent, a HTTP 415 error is returned.…
-
Hey @Dinonath Khan It's not currently possible to modify the questions on the native CSAT survey or to add additional fields. The following feature request tracks the ability to customize the form: JSDCLOUD-4534. There are Atlassian Marketplace options as suggested by @Valerie Knappalternatively, you can review the…
-
@Steven Vits From your screenshot the Body tab has data in it. Please set this to none and try your request again. The API is expecting an empty body and while this is a GET request, Postman will still send the data. This in turn is tripping up the API server that is rejecting the request.
-
Hey @Steven Vits A HTTP 403 error generally indicates a permission issue meaning the authentication was successfuly but the user does not have sufficient permissions to complete the task. If you are working with the Jira Cloud REST API or Jira Service Management Cloud REST API, make sure the service account has access to…
-
Hey @Darryl Lee - I came across this article by chance but saw it had some good points to it. I saw your update from earlier this year. While I've not used Bob Swift's CLI tool, but the command line tool cURL should work to pull the JSON data down. The rules themselves will be part of the rules array. The following should…
-
Hey @Puján Z That sounds about right with regards to the feature not being present on Automation rules configured for multiple projects. To confirm, when accessing a single project scoped automation rule via the project itself, you're able to see the Attach form action? Thanks, Andras
-
Hey @Puján Z - I apologize for the delay in updating this but I wanted to circle around on it. If you're editing the automation rule from the project itself as opposed to the Global automations page, the Attach form option should be available. The following feature request tracks the possibility of attaching forms for…
-
Hey @Puján Z Looking at your screenshot, the rule is being setup within the Global automation panel. Depending on the Rule details, your automation scope may be including Jira Software projects where Forms have not been rolled out yet. This can lead to certain actions such as Forms related actions not being available.…
