I can confirm that the way Scripted Fields are designed in ScriptRunner for Jira Cloud means that you must enter an issue Key in the Test Against Issue box and click the Test button to test the script first.
This is explained in more detailed in the documentation page here which lists the required steps to create a Scripted Field.
Once the script has been tested and has a valid return type then the Save button will become visible and available to use.
I hope this information helps.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events