Kristian Walker _Adaptavist_ Community Champion

Hi Ganesh, Unfortantetlyin Jira Cloud it is not possible to use JQL in workflow conditions or validators provided by ScriptRunner for Jira Cloud. This is because Workflow validators use the Jira Expression framework provided by Atlassian, and the Jira Expression Framework does not provide any way to use JQL in an…

Hi Jose, Can I please ask you to raise this issue as a support ticket here so that our support team can help investigate this and diagnose what is causing this behaviour for you? Regards, Kristian

Hi Nicholas, Can you please share a screenshot of the weblinks field on an issue in your instance so we can see this? Also, can you please confirm if the project type you are using is a team-managed project or a company-managed project? Regards, Kristian

Hi Lispa, In Jira Cloud the edit screen is issue view and behaviours work on this view and you can see what fields are supported on this view inside of our documentation page located here. Regards, Kristian

Hi Destri, The example library script here shows how to add users to an organisation when an issue is created, and this may be a useful reference guide to help you to create the script that you require. I hope this helps. Regards, Kristian

Hi Nicholas, I can confirm it is possible to copy the value from a field to the comments field using ScriptRunner for Jira Cloud. You would need to write a script which, first of all gets the issue and extracts the value from the WebLinks field to a variable. You would then be able to set this in the comments field of the…

Hi Ashok, Are you using Jira Cloud as mentioned on this ticket if so, behaviours use the UI modifications API provided by Atlassian. This means you can set fields required and as optional but can't check the field config schemes. We have an example of making fields mandatory here that may help. Regards, Kristian

Hi Kedar These Apis are for Jira dat center / server and will work on this but if on cloud they will not work. I was not aware of these data center apis myself so thank you for suggesting these. Regards, Kristian 

Hi Ri, I can confirm that this requirement could be achieved using ScriptRunner for Jira Cloud and the Script Listeners feature that it provides. The way this would work would be to configure a script listener mapped to your project. You would then add a condition in the conditions box to check if the issue type of the…

Hi Kedar, Having the transition screen dynamically set for certain issue types in the same transition by a script is impossible, as Atlassian does not provide any Rest APIs to do this. Regards, Kristian

Hi Crack Jack, I can confirm that inside the behaviours feature of ScriptRunner for Jira Cloud, it is impossible to access cascading select list fields. This is because the UI Modifications API from Atlassian, which Behaviours uses, does not support Cascading Select List fields. You can see a complete list of what fields…

Hi Tom, I can confirm in the example above the API causing the error was the Add User to Group Rest API and ass the linked documentation page states, Atlassian do not allow connect apps to use this resource. This means the API cannot be called from ScriptRunner. I hope this information helps. Regards, Kristian

Hi Christopher, I can confirm in Jira Cloud you can use the Workflow validators feature provided by Scriptrunner for Jira Cloud. Workflow validators use the Jira Expression framework provided by Atlassian, and you will need to use these to create the conditions you require. I can confirm we have an example on line 76 here…

Hi Logeshawari, Ok. You categorised this community answer for Cloud which is why the response was based on Jira Cloud. For Jira server, I would advise re-posting the question and tagging it for Jira server/ data centre. Regards, Kristian

Hi Muhammad, Unfortantetlyin Jira Cloud it is not possible to use JQL in workflow conditions or validators provided by ScriptRunner for Jira Cloud. This is because Workflow validators use the Jira Expression framework provided by Atlassian, and the Jira Expression Framework does not provide any way to use JQL in an…

Hi Osama, I can confirm the reason for this is that in ScriptRunner for Jira Cloud there are fewer built in scripts than compared to the on-premise versions due to the fact in Cloud Atlassian does not provide the same APIs required to make all the same built-in scripts. The Feature Parity page shows the differences between…

Hi Osama, I can confirm this is because you are using ScriptRunner for Jira Cloud and in the cloud version, we have fewer built-in scripts than in the on-premise versions due to Atlassian not providing the same APIs in Jira cloud to build the same built-in scripts. The Feature Parity Page shows the difference between the…

Hi James, In Jira Cloud you would need to call the Add user to a Group and Remove User from a Group Rest APIs to add and remove users from a group. However, in Jira Cloud it is not possible to get the last login time for a user as Atlassian does not provide this on the get User api. However, they provide the Users Last…

Hi Logeshwari, Reviewing the rest API inside of Jira Cloud, it shows that there is no single way to get this information. To do this, you first need to call the Get Dashboard Gadgets endpoint documented here to return a list of all gadgets on the dashboard and to store their ID's in a variable. You then need to call the…

Hi Shivendrta, Unfortantetlyin Jira Cloud it is not possible to use JQL in workflow conditions or validators provided by ScriptRunner for Jira Cloud. This is because Workflow validators use the Jira Expression framework provided by Atlassian, and the Jira Expression Framework does not provide any way to use JQL in an…

Hi Inger, I can confirm that the Behaviours feature provided by ScriptRunner for Jira Cloud can help to achieve your requirements. You would create a new behaviour mapped to the Create View and the Bug Issue Type to achieve this. You would then write a script that would check if the current user was in a member of the…

Hi Chandra, I can confirm we have many resources designed to help users who are new to using ScriptRunner for Jira Cloud. The first place will be to view the training videos on our documentation site here, which give a good product overview. The second is to watch our tutorial videos on our YouTube channel here and here.…

Hi Rebekka, This solution you have linked to is for Jira Server / Data Center and will not work in Jira Cloud as behaviours in Jira Cloud use Typescript and the UI Modifications API from Atlassian. Regards, Kristian

Hi David, I am glad we helped you to solve your requirement. Regards, Kristian

Hi Maria Your solution is for Jira Server / DC and will not work in Jira Cloud as validators use the Jira Expression Framework and not Groovy in Jira Cloud. I hope this helps. Kristian 

Hi David, I can confirm to make issueFunction work in Jira Cloud, you need to use the Enhanced Search Page provided by ScriptRunner for Jira Cloud. Once you have defined your filter on your enhanced search page, you can use it inside regular Jira in places like filters, boards and dashboards by following the steps below.…

Hi Josu, That JQL should work but you could also something like status changed to "Waiting for user" before startOfDay(-10) Regards, Kristian

Hi David, I can confirm that to achieve your requirement, you can use the Workflow Validators feature that ScriptRunner for Jira Cloud provides to make the assignee field required on the transition screen. Workflow validators use the Jira Expression framework provided by Atlassian, and I can confirm we have some examples…

Hi Josu, Thank you for your question. I the native JQL search in Jira you could run a query like issuetype = Incident and status = "In Progress" and status changed to "In Progress" before -10d In this query you can change the -10d to the number of days to check for an you can change the name of the issue type and status as…

Hi Katrin, I am glad I was able to help you solve your requirements. Regards, Kristian