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

When do I need getInput() in a validator and when do I not need it?

We're in the process of having to rewrite a large portion of our validator scripts to use getInput() instead of simply referencing the fields, and it's making me wonder exactly when I need to use it. An example:

// Ensure that issues with an SLA Violation have a SLA Violation Reason specified
// Implemented for Translations but seems relevant for all issue types

if (
    isCustomFieldInContext("SLA Violation", project, issueType) &&
    isCustomFieldInContext("SLA Violation Reason", project, issueType) &&
    #{SLA Violation} != "" &&
    #{SLA Violation Reason} == ""
    return false,"SLA Violation Reason must be specified";

return true;

I know that with those last two conditions I need to change them, e.g.:

if (getInput("SLA Violation"))

But do I need to do it for something like this?

if (resolution == "Done")

 Or any number of other types of built-in fields like Assignee, or Project, or issueType?

Essentially, I'm trying to determine when I can simply reference fields or variables without having to pull that info with a function. Is there a guide somewhere?

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events