Hey everyone,
I’ve been trying to use Script Runner with Jira Service Desk Cloud, but I’m hitting a roadblock. I wrote a simple script to add some example text to a description field. It works fine in a regular Jira Software project, but when I try to use it in Jira Service Desk (in the create view), nothing happens.
Does anyone know if Jira Service Desk Cloud supports Script Runner behaviors? I’m starting to wonder if there’s a compatibility issue or if I’m missing something obvious.
Also, if anyone has a basic script they’ve successfully used with Jira Service Desk, I’d love to see it. It would really help me troubleshoot my problem.
Thanks in advance for any help or insights!
I’ve encountered this issue before. Script Runner compatibility with Jira Service Desk Cloud is indeed limited. The create view in JSD operates differently from standard Jira projects, which can cause scripts to fail silently. One workaround I’ve found effective is using post-function scripts on the creation transition instead. This approach allows you to modify fields after the request is created, bypassing some of the JSD-specific limitations. Additionally, ensure you’re using the latest version of Script Runner, as Atlassian frequently updates compatibility. If you’re still stuck, consider reaching out to Script Runner support directly - they’re quite responsive and may have more specific guidance for your use case.
Hey Dave_17Sketch, i’ve had similar issues. script runner can be finicky with JSD cloud. make sure ur script is specifically set up for JSD, not regular jira. also, check ur permissions - sometimes that’s the culprit. if ur still stuck, the atlassian community forums have some good examples for JSD scripts. good luck!
As someone who’s worked extensively with both Script Runner and Jira Service Desk Cloud, I can confirm there are indeed some compatibility challenges. The key issue often lies in how JSD Cloud handles custom fields and scripts in its request types.
One approach that’s worked well for me is utilizing automation rules instead of direct Script Runner behaviors for JSD. These tend to play nicer with the JSD Cloud environment and can achieve similar results to what you’re after.
For your specific case of adding example text to a description field, I’d recommend setting up a JSD automation rule that triggers on request creation. This rule can then modify the description field as needed, effectively bypassing the limitations you’re encountering in the create view.
If you absolutely need to use Script Runner, focus on post-function scripts as mentioned by others. They’re generally more reliable in the JSD Cloud context. Just remember to thoroughly test any scripts in a non-production environment first to avoid any unexpected issues.