For Jira Cloud

The right people.
The right issues.
In view.

Bring your team into the loop with group watcher rules, personal project subscriptions, and a little less manual work.

Explore the guide →
Built for Jira CloudHosted on Atlassian ForgeYour Jira permissions still apply

A wider view.
A simpler workflow.

Connect teams to the work they follow, without adding the same people to every new issue by hand.

Bring groups into the loop.

Project admins choose Jira groups and individual users. Matching rules expand groups into eligible individual watchers.

Follow a whole project.

People can opt in to new issues in a project, or narrow their subscription to a component. Their choice, in one place.

Keep your focus.

Filter admin rules by components and issue types. Empty filters cover the project; combined filters must both match.

Give existing work a place in the picture.

Admins can explicitly apply a saved rule to existing issues with resumable backfill and saved progress. It sends no app addition-notification emails.

Notify only when you choose.

Optional rule addition notices are off by default. Jira controls eligibility and delivery; watcher status does not guarantee an email.

Choose who follows.
Let rules do the repetition.

  1. Set the scope.

    Open project settings. Choose groups or people and the components or issue types they should follow.

  2. Enable your rule.

    Save the configuration and enable it when ready. The app processes matching new issues within Jira permissions.

  3. Stay in view.

    Eligible accounts become individual watchers. Personal opt-in and historical backfill have their own controls.

Subscriptions, rules and progress in one place.

Four views for following new issues and applying rules to existing work.

Screenshot slot: project subscriptions.
Project subscriptionsManage which new project issues you follow.
Screenshot slot: settings and rules.
Settings and rulesReview enabled rules, recipients and filters.
Screenshot slot: rule editor.
Rule editorChoose groups, people, components and issue types.
Screenshot slot: existing-issue backfill.
Existing-issue backfillApply a saved rule and review its progress.

Fits your Jira.
Respects its controls.

The app runs on Atlassian Forge. Its current runtime has no external backend or declared external egress destination.

Read the security statement →
  • Permissions stay in place.Adding a watcher does not grant access to an issue. Project administration and user access are checked separately.
  • Configuration, not issue content.Application records retain identifiers, preferences and processing state, rather than issue summaries, descriptions or comments.