Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Cloud: PullingWorking with the contents of a scripted field


I have a post function that will create a subtask. I would like to use the value of a scripted field in the summary of the subtask.

  • How can we pull that value in the Scriptrunner "Create subtask" post function?
  • Use the field in a JQL?

1 answer

1 accepted

0 votes
Answer accepted
Kristian Walker _Adaptavist_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 13, 2020 • edited

Hi Michah,

I can confirm that currently that it is not possible to search in JQL for the values of Scripted Fields provided by ScriptRunner for Jira Cloud as this currently not a feature that we provide.

We can, however, confirm that we do have this on our roadmap as a feature request here and I would ask you to vote on this if this something that you are interested in so that our development team can see this and consider this as a feature to be added in future.

Also, I can confirm that Scripted Fields are calculated when an issue is loaded in Jira cloud and are a special field type rather than a standard custom field type like in Jira server. 

The reason for this is due to the API's that Atlassian provided being different between Jira Server and Jira Cloud.

This means that Scripted Fields are only designed to be viewed on issues and cannot be used inside of other scripts.

If you need to use these values inside of other scripts then you will need to use a Script Listener to calculate the value into a standard custom field on an Issue Updated event similar to the example we have here as this will then allow the value to be saved inside a standard custom field that can be used in other scripts.



Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events