Jira Cloud App
Dynamic Screen Rules
Build Jira forms that adapt to context, user role, and workflow state.
Show, hide, lock, validate, and auto-fill fields in real-time. Keep forms short, enforce data quality, and eliminate repetitive setup without code.
RUNS ON ATLASSIANFREE UP TO 10 USERS30-DAY FREE TRIAL
Problems this app solves
Dynamic Screen Rules addresses the core friction points teams hit with static Jira forms.
Overly long forms
Remove irrelevant fields and keep issue screens focused so users can complete tasks faster.
Inconsistent data quality
Apply dynamic required fields and validation rules to capture complete, policy-compliant data.
Manual data entry
Pre-fill defaults with Smart Values, field references, and date calculations to reduce repetitive work.
Confusing dropdowns
Limit options by context to prevent invalid selections and improve consistency across teams.
See Dynamic Screen Rules in action
Recommended rollout order for most teams: simplify forms, automate defaults, then enforce quality checks.
Show only fields that matter
Feature:
Use conditional visibility to reveal fields only for relevant cases, based on issue type, priority, component, or user context.
Benefit:
Forms are shorter and easier to complete, so users create issues faster with fewer mistakes.
Control field behavior with advanced conditions
Feature:
Show or hide fields, make them required, set read-only, or apply smart actions using complex conditions based on field values, user roles, and workflow status.
Benefit:
Teams enforce the right behavior at the right moment, reduce manual errors, and keep forms consistent without custom scripts.
Auto-fill smart defaults
Feature:
Use Set Field Value on Create and Transition screens with expressions like nextMonday(), currentUser(), date math, and field references.
Benefit:
Teams eliminate repetitive typing and keep values consistent without relying on static defaults.
Enforce quality before submit and transition
Feature:
Apply required rules and real-time validations based on dynamic context, including other field values, user permissions, groups, and current workflow status.
Benefit:
Teams enforce accurate data exactly when needed, reduce invalid transitions, and keep handoffs consistent across roles and responsibilities.
More features
Need the full configuration surface? Expand the list for advanced rollout and governance scenarios.
- Show or hide fields dynamically
- Make fields conditionally required
- Lock fields based on workflow stage or role
- Set dynamic default values on Create and Transition screens
- Advanced validations based on current performer, user role/group, and dynamic date rules
- Change labels and field descriptions contextually
- Limit dropdown options to valid choices
Business benefits for Jira teams
Dynamic Screen Rules improves data quality and form speed without forcing teams into hard-to-maintain ScriptRunner custom script workarounds.
Where to use each screen
Pick the screen by outcome, not by technical details.
Create screen
Issue view
Transition dialog
Rollout flow
Install and open configuration
Install from Atlassian Marketplace and open Project Settings → Apps.
Create first rule
Choose screen, field, conditions, and action. Save and enable it.
Test and roll out
Validate expected behavior, then copy the pattern to other projects.
Built for secure Jira Cloud operations
Rules are configured per project, billed via Atlassian Marketplace, and designed to work with native Jira permissions.
Dynamic Screen RulesJira Cloud app by Terano Apps
Adaptive formsValidation engineNo-code setup
Jira Cloud app with free tier up to 10 users and a 30-day trial for larger teams.
Forge-native foundation
Built on Atlassian Forge and aligned with Jira Cloud platform constraints.
Project-level rule isolation
Each project can define its own field logic without affecting unrelated teams.
Marketplace licensing model
Billing and subscription management are handled directly in Atlassian Marketplace.
Use case templates by team
Copy these patterns from documentation and tailor them to your workflows.
Software development teams
- Show bug-only fields such as Steps to Reproduce
- Require Root Cause only for high-priority incidents
- Lock Fix Versions in controlled workflow stages
- Pre-fill components or assignees by context
IT and service operations
- Enforce SLA dates for critical service requests
- Show escalation fields only when severity requires it
- Limit resolution options to valid outcomes
- Apply role-based visibility for sensitive operations fields
PMO and governance workflows
- Require approvals only above defined cost thresholds
- Validate date consistency for planning and delivery
- Keep compliance fields visible only in relevant contexts
- Standardize issue quality across multiple projects
Make Jira forms adaptive in under 10 minutes
Start with ready-to-use rule patterns, validate behavior in real-time, and roll out cleaner, policy-aligned forms across projects.
Install Dynamic Screen Rules