Skip to:

Marketplace

SubRule — Restrict Subtask Types for Jira

works with Jira Cloud

INSTALLS

No installs yet

SUPPORT

  • Partner Supported

TRUST SIGNALS

Showing details for Cloud

Key highlights of the appPick which subtask types are allowed under each parent work item type — enforced at creation, not just hidden in the UI

hero

Allowed subtask types per parent type

A simple per-project matrix: tick which subtask types are allowed under each parent work item type. Rows you leave untouched stay fully unrestricted — no accidental over-blocking

Blocked at creation, with a clear message

Enforcement is a Jira workflow validator on the Create transition — the issue view form and the REST API hit the same block, with a message naming both the subtask type and the parent type

Instant on/off that keeps your configuration

One switch attaches the validator to the project's workflow for you. Switching enforcement off keeps the saved matrix and leaves the rule inert, ready to re-enable at any time

More details

Every subtask type in your project can be created under every parent work item type — Jira has no built-in way to say "QA subtasks belong under Tasks, Design subtasks under Stories". SubRule adds exactly that, per project:

• A simple matrix: for each parent type, tick the subtask types that are allowed under it
• Rows you leave untouched stay unrestricted — no accidental over-blocking
• Enforcement is a Jira workflow validator on the Create transition: the same rule blocks the issue-view form and the REST API, with a clear message naming both types
• One Enabled switch: turn enforcement off without losing the saved matrix
• Team-managed projects are detected and shown a clear "not supported yet" notice

Setup requires a Jira administrator (the app attaches the validator to the project's workflow for you). Runs entirely on Atlassian Forge with no egress — your configuration never leaves your Jira site.

v1 covers creation only; type changes (Move/convert) are on the roadmap.

Resources

  • App documentation

    Comprehensive set of documentation from the partner on how this app works

Privacy and Security

Privacy policy

Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.

Partner privacy policy

Security program

This app is not part of the Marketplace Bug Bounty program.

Integration permissions

SubRule — Restrict Subtask Types for Jira integrates with your Atlassian app

Version information

Version 3.0.0for Jira Cloud

Release date
Aug 4th 2026
Summary
Initial release: subtask type rules per parent type, enforced at creation
Details

First public release.

• Per-project rules matrix: choose which subtask types are allowed under each parent work item type
• Enforcement via a Jira workflow validator on the Create transition — the issue view form and the REST API hit the same block, with a clear message naming both types
• One-click enable: the app attaches the validator to the project's workflow for you (Jira administrator required)
• The Enabled toggle preserves your saved matrix when switched off — re-enable any time
• Works on company-managed projects; team-managed projects are detected and shown a clear "not supported yet" notice

Payment model
Paid via Atlassian
License type
Commercial

Learn and explore

  • What’s Marketplace
  • App installation
  • About Atlassian
  • Atlassian resources
  • Search and ranking
  • Atlassian events
  • Atlassian foundation

Follow