Vishal Biyani Expert

can you show the screen shot of your params?

@Alex Burns with toDate you need to specify the date format. {{issue.statuscategorychangedate.toDate("yyyy-MM-dd").diff(now).minutes}}

This is my working curl. replace <your instance> and <encode_token> This should work curl --request GET \ --url 'https://<your instance>.atlassian.net/rest/api/3/search/jql?jql=project=CEE%20AND%20issuetype=Epic&maxResults=100&fields=summary%2Ccomment&expand=name' \ --header 'Accept: application/json' \ --header…

please add below 2 --request GET --header 'Accept: application/json'

Try with these 2 changes * remove &nextPageToken=<string> * Add --header 'Authorization: Basic ...' instead of --user flag

@Chandra Kakkireni Try something like this. curl --request GET \ --url '<a href="https://your-domain.atlassian.net/rest/api/3/search/jql?jql=project%20%3D%20HSP&nextPageToken=%3Cstring%3E&maxResults=100&fields=key,summary" target="_blank" rel="nofollow noopener…

@Jonathan Grove Have you looked at using Workflows? Check this article and see if this helps Introduction to Jira Workflows | Atlassian

@Hussein K_ if you are using external systems import then summary needs to be specified.

Thanks. I was using it the wrong way. Also, the JQL Functions page doesn't seem to be having this function. 

@jeroen_wilmes I don't think JQL natively supports During unless you are using some plugins. Refer this link for list of functions that JQL supports JQL functions | Jira Cloud | Atlassian Support

@zain Can you share the screen shot of the automation that you have? If one task need to be created at a schedule that is different for other two tasks, what is the challenge is creating 2 different automations?

As you are creating Story or Task, parent key needs to be Epic. It is not possible that Epic will have key = MANSI.

@Mansi Gusain Your parent key should be like MANSI-123 etc "parent": { "key": "MANSI" },Can you check this?

difficult for me to say. Better to reach out to Atlassian support and have them take a look

I think if will be better to raise the issue with Atlassian support in this case. https://support.atlassian.com/contact/#/

This doesn't look to be complex query. Can you try removing "Customer Reference[Short text]" ~ "1948" and see if it allows you to switch to Basic?

@Denitsa Boiadjieva Can you share the JQL that is giving this error?

Let's assume you have Story or a Task and subtasks are created under it. When Story/Task is transitioned to Design & Development, the automation kicks in. Instead of branching for Current Issue, if you branch for subtasks the focus will shift to each subtask. Add and if to check Status and Summary match the conditions…

@Renata Klimiato click on more options and use this json to update the label field. this will work. { "fields": { "labels": [ "operational_excellence"] } } and as John suggested, adding a re-fetch issue after the checking for sub-task will also help

@james_vanderhaeghe What is your trigger in the automation? Are you using lookup issues component to JQL? Can you share screen shot of your automation to understand where the issue might be?

So, if the issue is getting created, however, the response from JIRA Cloud is taking more time to come back, due to some network issues or whatever, then one of the option is to try and increase the timeout and see if it helps. Other than that, the other option is to check recently created issue if the request timed out.…

Can you try using below and see if you get the request id? // Extracting Jira's request ID from headers const jiraRequestId = response.headers['x-arequestid'];

@Alokkumar Sahu Yes you will need to validate your access in Sandbox with help of administrator

in JQL after = JIRA would be giving some options. Can you see if you see April Release 2025 given by JIRA auto sense and try to use that?

This is strange. Can you share the screen shot of the issue key where you see the fixVersion and the JQL query? Black out any sensitive information. But I will need to see the issue key and associated fixVersion in the issue key along with your JQL query.

The way the details have been dumped can't be comprehended. With the availability of tools like ChatGPT this task has become lot easier. Looks like you are using Axios with Node.js. The payload that is being used may be too big. Can you try this code and see if this helps you move forward? if this works, then you can…

@Zhishang Zheng Can you share more details like which JIRA APIs are you using? What is the payload that you are passing?

@Fabian Gropp As I don't have your template, I created a basic template, which has release_version_placeholder in title and release_version_placeholder in body apart from an H1 title. With this complete solution, confluence page is getting created using the template and is release_version_placeholder is getting replaced by…

@shravan_moota1 Refer to this url https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-post

@Mandapati Niveditha To rule out that issue is due to some filters set on release page, can you run the JQL fixVersion = <your version#> and see if it returns the issues tagged to the version#