Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This section has use cases which help you in understand the usage of Validators provided by JMWE.

...

  • (lightbulb) Block the creation of a Bug if no Attachment is provided.

    Expand
    titleSteps


    Panel
    • Add the Scripted (Groovy) validator to the Create transition.
    • Write the following in the Groovy script

      Code Block
      languagegroovy
      linenumberstrue
      try {
        return issue.get("issuetype").name != "Bug" && issue.getModifiedFields()?.get("attachment")?.getNewValue()?.size() > 0
      } catch (Exception e) {
        return false
      }




  • (lightbulb) Validate the Cascade select for values in parent and child select dropdowns

    Expand
    titleSteps


    Panel
    • Add the Scripted (Groovy) validator to the transition.
    • Write the following in the Groovy script

      Code Block
      languagegroovy
      linenumberstrue
       issue.get("Cascade")?.get(null) != null && issue.get("Cascade")?.get("1") != null




  • (lightbulb) Block the approving of the Change request if it has no confluence page linked

    Expand
    titleSteps
    • Add the Scripted (Groovy) validator to the Approve transition.
    • Write this content in the Groovy script.

      Code Block
      issue.getRemoteLinks("confluence").size() > 0


    • Type the error message in Error message, to display if the validation script returns false


...

  • (lightbulb) Block the transition of the Epic to Closed status, if its stories aren't closed.

    Expand
    titleSteps


    Panel
    • Add the Linked issues status validator to the Close transition.
    • Select the issue link type is Epic of from the Issue Link Type field.
    • Select the statuses the linked issues must be in, from Statuses

    • Add the error message, "The Stories of the Epic are not yet resolved"



...