If someone is under the beta, will they automatically start getting charged once it is GA? Or will there be advanced notice that users have X number of days to opt-out before the beta is discontinued?
Once we move to GA, we will give plenty of notice letting you know about pricing (emails, pop ups within the product and plenty of time to make a decision. In short, no billing surprises :)
I'll just pile on with everyone else: With not even a ballpark figure of what this could potentially cost in the future, I'm not willing to put any effort into this. It seems you all want us to invest a lot of time and effort into this and then will spring (another) exorbitant fee on us to keep going with this after the change cost becomes too high (due to all the time and information we invest during the beta). Feels like this is taken straight out of the Drug Dealer's Handbook.
I get the frustration and I promise that is not the intention. It is our main priority to get the pricing and packaging sorted and communicated to customers as soon as possible. The product remains free until then. Next time around, we will be more proactive here.
I haven't read the Drug Dealer's Handbook (yet :) but if you have any other questions about JPD, please let me know. More than happy to jump on a call any time.
Well, once you all do post the pricing and packaging—and if the cost appears reasonable for what this is—I may consider rejoining the beta. But for now, it has been canceled from our company subscriptions.
It looks very promising, but we are not going to fiddle with it without knowing anything about:
pricing asking us to take a leap of faith is... well a bit to much. How will it be calculated? Like service desk? Everyone who wants to have a look at it needs a license or is it more in line with what productboard offers as licenses per maker?
sharing roadmaps with external stakeholders and the effect it has on pricing does everyone require a license to view the roadmap?
Not giving any new information about it in the slightest for months is a bit weird to me (saying sorry we have no information is not new information).
I'm not even sure what is keeping you back to not be able to come up with a pricing strategy for your new product since april. Kind of raises some questions on my side really. Only 2 months left untill January when it might not be free anymore. So what's the hold up? And what is your definition of "plenty of time".
It also got me thinking how does this lack of pricing information skew your usage metrics for your new product? As I can read in this thread (and probably a lot of lurkers around) this is blocking a lot of people for giving it even a spin.
In conclusion we are not going to use it and as soon as the pricing is known it will be compared against other products out there.
I hear you. It is as frustrating for me to write the same response as it for you to read it.
It has taken more time than we'd like. Building a new product isn't simple but ideally pricing would be shared earlier. We are very looking forward to the next step and hopefully you'll give it a try once we announce pricing and GA date.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
The products looks great and it answers a need we are trying to solve now but, as others before us, we cannot commit of invest time untile there is some clarity on the pricing
Hi @John McKiernan - like everyone else, we're eager to check it out, and waiting until we know if it will be worth our time. While I have the same questions about price & sharing with externals, one thing that might help us try it out now, is if a conversion would be available should we not continue?
On page one of this FAQ, it mentions
However, should Jira Product Discovery not find product-market fit, users will not lose their data. JPD projects will simply be converted into a kanban or scrum project in Jira Software.
Would this same simple option be available should PD move from Beta to GA?
For us, it's currently only a question of whether or not we build our POC with a standard Kanban template, or Product Discovery. Knowing that the work would be easily converted makes it much easier to embrace the PD Beta right now. :)
We love the JPD but hoping its pricing will be much lower than monday.com. We use monday.com for similar features provided by JPD so we're hoping to eliminate the use of monday.com once JPD is in its GA stage.
When JPD goes to GA, can Ideas be moved to projects without losing Insights? We created a single project to use so that we wouldn't have to rebuild any fields across multiple projects.
In regards to contributors vs creators with the pricing model for JPD.
Some people at our company do not use Jira at all, and would not be added to avoid unnecessary user license costs. Do I understand correctly that they can still be a JPD contributor though? We give them an account to JPD only, and there is no cost to the business?
Yes you can be a JPD contributor without any costs. At this point, they will need some sort of Atlassian account to be a contributor in JPD but it doesn't need to be a paid account.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Do we know when this is going to be sandbox-capable? Seems like if you want people to play with things, we should be allowed to do that in a place where we play with things :)
This looks like a great product and one that many have been waiting for!!
Is it safe to trial the Beta "Jira Product Discovery" integrated with an enterprise size Jira cloud , or should we keep that isolated until GA? How much Jira data can it modify?
Atlassian Team members are employees working across the company in a wide variety of roles.
February 17, 2023 edited
@Andre Groen there are thousands of customers using Jira Product Discovery today, and some pretty big instances. HOWEVER, in my opinion you should start with a pilot to test it out at smaller scale before going all in. Sometimes in very big instances there are things like add-ons etc. that can come in the way.
However the product is pretty well isolated from the rest of Jira - it's basically a new team-managed project type and extra functionality that only works in this project. We've seen that it can sometimes mess up with Automation rules if they were set up using fields by names (and the projects created by users contain the same field names). That's about the only side effect to the rest of Jira that I'm aware of.
I know the naming of Jira products can be confusing so just want to clarify what you mean here.
Do you just want to switch from a JIRA Product Discovery project to a Jira Software Project? If so, you can just use the app switcher or project switcher as per screenshot below.
Or if you are asking how to move from Jira Product Discovery beta to Jira Product Discovery GA (i.e a free or standard edition) - that's not ready just yet but we will have news on this soon.
56 comments