📣 Incoming changes: Notifications for Contributors

[#1]

Jira Product Discovery isn't just for product managers - it works best when customer-facing colleagues, subject matter experts, and cross-functional partners are in the loop too. That's exactly what the Contributor role is for.

But here's the problem: Contributors who watch ideas haven't been getting notifications. They can create ideas, comment, vote, and join conversations - yet when something changes, they often hear about it through a side-channel ping or an mention workaround instead of a proper notification.

We're fixing this. Soon, Contributors who watch ideas will receive notifications for meaningful updates - even without a paid Jira license. No more gaps, no more guesswork. JPD collaboration becomes predictable for everyone involved.

What’s changing

After this rollout, contributor-watchers will receive the same supported watcher notifications that licensed users already receive, as long as they have access to the idea and their personal notification preferences allow it.

More specifically, this applies to users who:

• are set up as contributors in Jira Product Discovery,
• have access to the relevant JPD project and idea,
• are watching that idea, and
• have notification preferences enabled for the supported events.

When it’s happening

The rollout window for this change is May 18, 2026 to May 27, 2026.

As the rollout progresses, eligible contributors will begin receiving supported notifications without needing any action from admins or end users.

If your site is on the continuous release track, you can start using the feature straightaway. If it is on the bundled release track, it will be available on:

• Bundled track (production): Jul 14, 2026
• Preview track (sandboxes): Jun 9, 2026

If a contributor starts receiving notifications and prefers not to, they still stay in control:

• They can update their personal notification preferences.
• They can also stop watching a specific idea.

So while notification reliability improves, user-level controls remain the same.

A quick reminder: the JPD permission model

Since this update specifically addresses contributor notifications, it’s a good time to revisit the two core JPD roles.

Creators

Creators are licensed JPD users. They typically include product managers and others who actively run the discovery and prioritisation process. Creators can:

• create and edit ideas,
• manage views, fields, and settings,
• configure the project or space,
• and use the full Jira Product Discovery experience.

Contributors

Contributors are free users with limited access to the product, designed for broader collaboration. Contributors typically can:

• create ideas view ideas they have access to,
• react, and vote on ideas
• add comments and insights

Contributors cannot manage the full product setup the way creators can, and they don't require a paid JPD license.

How to engage stakeholders without granting role and space access?

You can use published views when stakeholders need visibility, but don’t need access to the whole JPD space. A published view is a real-time, read-only display of your roadmap that shows only the ideas and fields you select.

• For stakeholders with an Atlassian account, share the view with specific people, groups, or everyone on your Atlassian site.
• For stakeholders without an Atlassian account, use a public link so they can view updates without signing in.

This is best for leadership, customers, partners, or cross-functional teams who need alignment and status updates. If they need to comment, vote, watch ideas, or receive JPD notifications, they’ll need an Atlassian account and the right JPD access.

Best,

Olga Springer

Senior Product Manager

Jira Product Discovery

[Denis Paul]

That's great news! We've just implemented a workaround: https://community.atlassian.com/forums/Jira-Product-Discovery-articles/Hybrid-stakeholder-notifications-in-Jira-Product-Discovery/ba-p/3218948 😂

We're currently experiencing an issue that started around the same time as this rollout (May 18–27) and I'm wondering if it might be a side effect.

In our JPD project, users who are not watchers of specific ideas and have no direct involvement with them are receiving notification emails for every change made. These are Contributors who should not be notified at all based on their watch/subscription settings.

We've already ruled out our project automations as the cause.

Could this be related to the contributor notification rollout — for example, a broader-than-intended audience being included in the notification logic during the rollout phase? Any guidance on how to troubleshoot or confirm this would be appreciated.

Thanks!

[Olga Springer]

Hey , 

Notifications that were previously blocked for contributors without a paid Jira license are now working. In your case, you may have additional automation triggering some of those emails - it might be worth checking.

If the problem persists and you can't find the cause, please contact Atlassian Support.

Best,

Olga Springer

Senior Product Manager