Skip to main content

Creating Your First Rule

This guide walks you through creating a rule from start to finish. You'll learn each step in the configuration process and understand what each option does.

tip

By the end, you'll have a working rule and the knowledge to create more sophisticated rules on your own.

Before You Start​

warning

Prerequisites checklist:

  • ✅ Project administrator access to your Jira project
  • ✅ Access to Dynamic Screen Rules configuration panel
  • ✅ Fields already added to the appropriate Jira screen
info

New to Dynamic Screen Rules?

The Rule Creation Process​

Creating a rule follows these steps:

  1. Select Screen - Choose where the rule applies (Create/View/Transition)
  2. Choose Target Field - Select which field the rule will affect
  3. Define Scope - Specify which issue types the rule applies to
  4. Select Action - Choose what happens when conditions are met
  5. Configure Parameters - Set action-specific details
  6. Define Conditions - Set when the rule triggers
  7. Save and Test - Activate the rule and verify it works

Let's walk through each step with a practical example.

Example: Show Root Cause for High-Priority Bugs​

info

Business scenario: Your team wants to capture root cause analysis for high-priority bugs, but this field clutters the form for routine bugs. You want Root Cause to appear only when Priority is High or Critical.

Goal: Show the "Root Cause" field only when creating Bug issues with Priority = High or Critical.

Step-by-Step Rule Configuration​

  1. Select Screen​

    First, choose where the rule should apply.

    1. Open the Dynamic Screen Rules configuration panel
    2. Click the tab for the screen you want: Global Issue Create, Issue View, or Issue Transition

    For our example: Click Global Issue Create (we want the rule to apply when creating issues).

    info

    Why this screen? We want to control field visibility during issue creation. Global Issue Create is the best screen for progressive disclosure where fields appear as users make selections.

  2. Click Add Rule​

    1. Click the + Add Rule button (typically in the top-right corner of the rules list)
    2. The rule configuration form appears

    You're now in the rule builder.

  3. Choose Target Field​

    Select the field that the rule will affect.

    1. In the rule form, find the Target Field selector (usually the first option)
    2. Click the dropdown to see all available fields
    3. Select your target field

    For our example: Select Root Cause from the field list.

    info

    Only fields already on the screen appear in the target field list. Dynamic Screen Rules modifies existing fields—it doesn't add new fields to screens. Add fields to screens through Jira's native screen configuration first.

    warning

    Can't find your field? The field must be added to the Jira screen first. Navigate to Project Settings → Screens to verify the field is on the Create screen.

  4. Define Scope (Issue Type Filter)​

    Scope determines which issue types the rule applies to.

    1. Find the Scope or Issue Type section in the rule form
    2. Select which issue types should trigger this rule
    3. Leave empty to apply to all issue types, or select specific types

    For our example: Select Bug from the issue type list.

    Why scope matters: Rules can target specific issue types without affecting others. Our Root Cause field is only relevant for Bugs, not Stories or Tasks, so we limit the scope to Bug issues.

    tip

    Multiple issue types: You can select multiple issue types if the rule should apply to several types (e.g., Bug and Incident).

  5. Select Action​

    Choose what the rule does when conditions are met.

    1. Find the Action section in the rule form
    2. Select an action from the dropdown:
      • Show / Hide Field
      • Make Field Required
      • Lock Field (Read-Only)
      • Set Field Value
      • Change Field Label
      • Change Field Description
      • Limit Field Options

    For our example: Select Show / Hide Field.

    Why this action? We want the Root Cause field to appear when conditions are met and remain hidden otherwise. Show/Hide is the perfect action for progressive disclosure.

  6. Configure Action Parameters​

    Some actions require additional parameters.

    For Show / Hide Field:

    1. Behavior: Show field when conditions are met (this is typically the default)
    2. Most Show/Hide actions don't require additional parameters
    info

    Alternative behavior: Some configurations let you choose "Hide field when conditions are met" instead. For our use case, we want "Show," so the field appears when Priority is High or Critical.

    Other actions may have parameters:

    • Set Field Value: You'd specify what value to set
    • Change Field Label: You'd specify the new label text
    • Limit Field Options: You'd select which options to show or hide

    For our simple example, Show/Hide typically requires no additional parameters beyond the condition.

  7. Define Conditions​

    Conditions specify when the rule triggers.

    1. Find the Conditions section in the rule form
    2. Click + Add Condition to add a condition
    3. Select the condition type (field-based, context-based, or user-based)
    4. Configure the condition details

    For Our Example - Field-Based Condition:

    1. Condition type: Field-based
    2. Field: Priority
    3. Operator: Equals
    4. Value: High

    Add a second condition for Critical priority:

    1. Click + Add Condition again
    2. Field: Priority
    3. Operator: Equals
    4. Value: Critical

    Result: The rule triggers when Priority = High OR Priority = Critical.

    info

    Multiple field-based conditions use OR logic. If ANY condition is met, the rule triggers. This means "High OR Critical" without needing complex logic configuration.

    tip

    No conditions? If you don't add conditions, the rule applies to all issues of the specified scope (all Bugs in our example). This is useful for rules that should always apply to certain issue types.

  8. Review Your Configuration​

    Before saving, review the rule summary:

    • Target field: Root Cause
    • Screen: Global Issue Create
    • Scope: Bug issue type
    • Conditions: Priority equals High OR Priority equals Critical
    • Action: Show field

    Mental check:

    • ✅ Does this match your business requirement?
    • ✅ Will it trigger in the right situations?
    • ✅ Are there edge cases you're missing?

    If everything looks correct, proceed to save.

  9. Save the Rule​

    1. Click Save or Create Rule button (button text varies by UI)
    2. The rule is created and automatically enabled
    3. You return to the rules list with your new rule visible
    info

    Rule naming: The system auto-generates a descriptive name based on your configuration, like "Show Root Cause when Priority = High OR Priority = Critical (Bug)."

    You don't manually enter rule names—the system creates clear, readable names from your configuration.

  10. Test Your Rule​

    Now verify the rule works as expected.

    Testing checklist:

    1. Open the Create Issue dialog - Click Create in Jira's top navigation
    2. Select the issue type in scope - Select Bug as the issue type
    3. Observe initial state - The Root Cause field should be hidden (Priority is empty, conditions not met)
    4. Trigger the condition - Select Priority = High
    5. Verify the action - The Root Cause field should appear immediately
    6. Test the other condition - Change Priority to Critical - The Root Cause field should remain visible
    7. Test non-matching condition - Change Priority to Low or Medium - The Root Cause field should disappear immediately
    8. Test different issue type - Change Issue Type to Story or Task - The Root Cause field should not appear even if you set Priority to High (rule is scoped to Bug only)
    tip

    Rule working correctly? Congratulations! You've created your first rule. The form now adapts to user input, showing the Root Cause field only when relevant.

What You've Learned​

tip

Congratulations! You now have the foundational knowledge to create any rule in Dynamic Screen Rules.

You now know how to navigate configuration, create rules step-by-step, set up target fields and scope, define conditions and actions, and test your rules. This foundational process is the same whether you're creating simple visibility rules or complex multi-condition rules with advanced actions.

Next Steps​

Continue your learning journey:

  • Explore All Actions - Guide to all seven actions: show/hide, required, lock, set value, change labels, limit options, and more
  • Master Conditions - Deep dive into field-based, context-based, and user-based conditions
  • Field Validations - Enforce data quality with 15 validation types across presence, date, number, and text categories
  • Smart Values - Compute field values automatically using expressions, date math, and conditional logic
  • Use Cases & Examples - Ready-to-use configurations for common scenarios
  • Managing Rules - Enable, disable, edit, delete, and organize your rules