Kristian Walker _Adaptavist_ Community Champion

Hi Esther, I can confirm you will need an App as Nic has said as this kind of query is not possible out of the box in Jira Cloud. If you do not want to purchase the full ScriptRunner for Jira Cloud App then you can look at our Enhanced Search app which provides just the JQL functions. I hope this helps. Regards, Kristian

Hi Erika, I can confirm that this is not possible t create a variable that can be used in a JQL search as Atlassian does not support variables being passed into a JQL query. I can confirm that when you create an issue you can reference the issue object which comes in the binding of your script and below this you will be…

Hi Esther, I can confirm that ScriptRunner for Jira Cloud provides the dateCompare() JQL function as documented here that can be used for searching against dates and the documentation page linked provides examples of how to use this query in Jira Cloud. Also it is worth noting in Jira Cloud the enhanced search queries can…

Hi Alexy, I can confirm that what Kate has said is correct and that the Get Issue API which you are calling does support using the fields queryString Parameter and this is documented inside of Atlassian Documentation for this API here. I have tested the code Kate has provided and can confirm if you include this in your API…

Hi Chirada, You are welcome. If this issue has been resolved, can you please mark this answer as accepted so that other users can please mark this example as resolved so that other users can see that this a correct answer. Regards, Kristian

Hi Chiara, Please note I am doing my best to help yourself as much as I am able to and I apologise if you do not find my responses helpful. I can confirm that I have included the script I used here and you will be able to take this script and to use this as an example to see where it worked for me when I used this script…

Hi Chiara, I have tested this using the condition shown here on line 51 and then I ran the script console script on the script console with just specifying the value for the second field and not the first field and it allowed me to create the issue so it is working as expected from my point of view. If it is not working in…

Hi Ricardo, I can confirm to see the rest call and the screen I used you will need to go to the script Console page in your instance at the URL of <JiraCloudURL>/plugins/servlet/ac/com.onresolve.jira.groovy.groovyrunner/script-console?s=com.onresolve.jira.groovy.groovyrunner__script-console and then clicking on the link…

Hi Chiara, This is the correct expected behaviour with the expression one of the fields must have a value and if one of the fields does not then the validator will fail and will not allow the issue to be created. This is how Jira Expressions are designed to work. Can I ask you to clarify what behaviour are you expecting to…

Hi Ricardo, Can I please ask are you asking for a screenshot of the script I ran from the script console or the script from the expression specified in the workflow validator? Regards, Kristian

Hi Chiara, I see you are using a Curl rest call and I cannot advise on how to use Curl as this is not related to ScriptRunner. I can confirm to see the rest call I used you will need to go to the script Console page in your instance at the URL of…

Hi Ricardo, I have just checked again and can confirm this error message you are getting is the correct message that will be shown when one value is not specified and that validators only show the history for when an execution fails due to how they have been defined. This means if you save the validator and create an issue…

Hi Kelly, Thank you for your question. I can confirm that with ScriptRunner for Jira Cloud then it is possible to write a script which can be used to programmatically create multiple subtasks below an issue. I can confirm we have an example of how to do this in the Adaptavist Script Libray located here and you will be able…

Hi Ricardo, Can I please ask you to remove the validator and to recreate as I like I have said I have tested your validator and it works as expected in my instance and checks all three fields so this must be caused some configuration in your instance and I cannot advise further on this as I have validated this and proved…

Hi Chiara, I can confirm the condition I used for my Jira Expression was the one shown here on line 51. As for how I created the validator then I did this by using the expressions Also for the script, I used to test creating an issue from the Script Console this was the one which you can see by going to the script Console…

Hi Chiarra, Thank you for your response. I have done a test creating a new issue from the Script Console and can confirm that if when creating an issue that you do not specify a value for one of the fields in the validator in the body of the request to create the issue that the validator will fail and the issue will not be…

Hi Ricardo, Can you please edit your validator expression as it looks as if you have a cartridge return line feed at the end of the expression which is causing the validator to fail. I have checked the logic of your validator in my local instance and can confirm that this valid and that it will work both in a workflow…

Hi Chiara, Thank you for your question. I can confirm that Workflow Validators inside of ScriptRunner for Jira Cloud are defined using the Jira Expression Framework as documented in the Atlassian API documentation page located here or in the documentation page located here which explains how to add in a new validator to…

Hi Ricardo, I have also done a test creating a new issue from the Script Console and can confirm that if when creating an issue that you do not specify a value for one of the fields in the validator in the body of the request to create the issue that the validator will fail and the issue will not be created. This is how…

Hi Ricardo, I have just done a test using two labels fields and a multi-line text field and can confirm that your expression is valid and can confirm that If you configure a script runner validator using this with the expression defined on a single line then it works. When I create a new issue to run the create transition…

Hi Ricardo, I can confirm that it is possible with *ScriptRunner for Jira Cloud* to check more than one field as we just use the *Jira Expression* framework that Atlassian provides to run expressions. If you are able to confirm for me what type each custom field you are using is then I will be able to check in my local…

Hi Ricardo, Thank you for your question. I can confirm that Workflow Validators are defined using the Jira Expression Framework as documented in the Atlassian API documentation page located here or in the documentation page located here which explains how to add in a new validator to your workflow. I can confirm that when…

Hi Slarkin, I cannot say if Atlassian will address them and this is something that our product owner may consider adding to ScriptRunner for Jira Cloud in future if users vote on this request but we cannot guarantee if we will ever add any features suggested in the backlog. Regards, Kristian

Hi Teresa, I can confirm if you are using ScriptRunner for Jira Cloud then you can achieve this requirement using a Scripted Field and I can confirm we have an example in the documentation page here that explains how to do this. Using the steps on this page then you will be able to create a Scripted Field which when the…

Hi ZB, I meant that you will need to raise a ticket with Atlassian which you can do here as the Jira Expression Framework is provided by Atlassian. I can confirm we have a public backlog here where you can suggest features that you are interested in but we do not have any dates on when we will have the same features as the…

Hi ZB, I believe this a limitation of the expression framework if it is not recognising the field correctly. As it is Atlassian who produce the expression framework, then I would be raising a support ticket with them as they will be able to confirm if there is any other way to do this. I can confirm there are methods that…

Hi ZB, Please note that my response was designed to help yourself and I apologise if you feel I am not helping yourself. I can confirm that if the field is a string then Atlassian will not allow this to be parsed to a date in the expression framework that they provide in Jira cloud as they only allow the methods which they…

Hi Des, You are welcome. Regards, Kristian

Hi Z B, Thank you for your question. I can confirm that the reason why you are getting the error is due to the fact that your code for the Workflow Validator is not valid code and I can confirm that Workflow Validators are defined using the Jira Expression Framework as documented in the Atlassian API documentation page…

Hi Mengmeng, I can confirm the answers from answers from Kagithala are correct and you can download Project Configurator for Jira Server / Data Center here and we have a guide how to install it in the documentation here. As for Jira Cloud then I can confirm that currently we do not provide a version for this but we are…