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

Scriptrunner: how to have different scripts for different contexts for the same custom field

Hi there

I would like to have 1 custom field in Jira UI with 2 contexts, so that each context refers to a different Scriptrunner Scripted Field, atlhough with the same name, but different script. Any idea, please?




1 answer

0 votes
Nic Brough -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 03, 2021

The scripts are not kept in the context, they apply for the entire field.

You will need to create a new field for each different script.

Thanks Nic. That is what I thought, but the previous Jira admin did it in the Jira I am managing now. There are  2 scripted fields, each of them for a different context, so in Jira UI There is only 1 custom field with 2 context...

This was previously possible in SR for Jira DC. Newer version of SR (v > 6.x) has removed the possibility to have different scripts for each contexts for one scripted field. Creating new field for each script is not ideal and scalable solution. 

For example a scripted field called 'Info' can render different HTML messages for different contexts based on different requirements. Creating new field for the same purpose is not a scalable solution, especially when they have the option to keep the same name for field. 

Like # people like this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events