I'm on the FREE plan and I get a message I can't add the Jira Product Discovery app

[Marcelo Lopez]

Anyone know what would keep Atlassian from permitting activating Jira Product Discovery when you're on the FREE PLAN.

Further, I could swear I had access to it, but for some reason it's now gone.

[Jessica · Accepted solution]

Hello @Marcelo Lopez

We don't have access to your site, but from the site details te****a.atlassian.net, it seems the Jira Product Discovery is currently active, which was reactivated at 26 Jun 2026 by one of our colleagues from the billing team.

From the latest comment, it seems you got the product back, but if you need further assistance, feel free to get back at the ticket CA-****6.

For any other issues related to your subscription (reactivate, deactivate product, change plans, etc.) please feel free to open a ticket directly at https://www.atlassian.com/company/contact/purchasing-licensing?redirectSource=sac-wac-redirect#/, so our billing team can help you with those topics (For any plan tier) :).

Cheers,
Jessica

[Walter Buggenhout]

Hi @Marcelo Lopez,

It is very well possible that these issues are related. There is - indeed - no reason why you wouldn't be able to add JPD to a free Atlassian site.

I have - however - seen it happen that people do start a trial of the product, add to many users to stay on the free plan and then fail to either add payment details or reduce the number of users to get back into the limits of a free plan (JPD free allows for 3 creators only). At that point, the app may get disabled from your site, which then disallows you to re-activate it.

If this is what happened, only Atlassian support would have the power to investigate and unblock you. I'll pull them into your request so they can have a look.

Hope this helps! 

[Marcelo Lopez]

Sadly, I wish you were right, but no. I've never had any more than 3 persons activated on my plan, and presently there are only 2.

Still, this situation doesn't JUST affect JPD, but a great many other things as well. It really stinks that this is even a THING. I can imagine that there are folks to whom this applies to them. 

However, since Atlassian knows how many active users are configured for ANY instance at any given time, and also has access to said history of active (or rather, CONFIGURED FOR ACCESS) users, this design is not only kludgey, it smacks of not being fully thought through. 

Coming from not only software development, but also product management, I'd kinda think the access model would've been better fleshed out after all these years.

Up to this moment, no one from Atlassian support has reached out.

I appreciate the observations though, @Walter Buggenhout .

[Marcelo Lopez]

Thank you! I see that it must've been reactivated. I was OOTO for a few days since I posted my original question. Thanks to you for reactivating it.

Much obliged.

Marcelo