JPD Creators should be able to use Jira Software for "free"

[Alexandre Krammel]

Creators in JPD most of the time will also need to access Jira Software Projects, since Product Owners work on Discovery but also on the Delivery managed at Jira Software

As JPD uses Jira Team-Managed engine, most of the features of JPD can be achieved using a Team-managed project, what leads to not subscribing to JPD.

Despite some added features in JPD compared to a Jira Team-Managed project, licensing a user in JPD for US$ 10.00 and having to license such user also at Jira Software for US$ 7.75 (Standard) means licensing the user twice for the Jira Core engine.

Like a Jira Software licensed user (US$ 7.75) is able to use also Jira Work Management (US$ 5.00) Projects for free, a JPD licensed creator (US$ 10.00) should be able to use a Jira Software Project (US$ 7.75) for free.

Makes sense?

[Sushma Jampani]

Thankyou for your quick response.

[Alex Tsai]

Many options for Atlassian to monetize JPD so agree 120%. Atlassian really need to revisit how they are pricing Product Discovery. The current pricing model doesn't work and I'm inclined to use another tool which is ashame.

[Tanguy Crusson]

Interesting way to look at it. Should I only buy one song from an artist and get all the other ones for free? After all, they were created using the same instruments 🙃

We totally understand if the current pricing model isn't right for you - and we know we won't be able to please everyone. So far, 3 months after GA, we've been able to validate most of our early assumptions when creating the pricing and packaging model, so I don't think this model is going to change in the short term. That being said, we're always open to feedback and making sure the price matches the value is something we'll keep looking at. 

[Alex Tsai]

At a minimum, contributors should be able to edit their ideas without having to be a creator. The expectation that a contributor will be able to capture their idea fully is not realistic. Other similar products allows contributors to create and edit their ideas. Worth exploring. 

[Alexandre Krammel]

@Tanguy Crusson It is not a matter of paying one music and getting all the others.

The scenario is a group of Product people for which we would pay US$ 10 for each JPD seat, but must still pay the full price of US$ 7.75 for their seats at JS.

Why should it be different?

Because most of the JPD features come from the Jira Core, which is been already paid in the JS seat.
That is also why with the JS license it is possible to have most of JPD features in a standard JS Project, since both are built on the same Jira Core. And for the added features of JPD like prioritization formulas and matrix view, there are Add-ons like Backlog Prioritization for Jira. Pro which will cost 20% of JDP, even considering add-ons must be licensed for the full number of JS users. 

Of course, if you and customers are confortable with the pricing and packaging model, just keep it.

Regards

[Sheri Widler]

We need contributors to be able to edit, very rarely are they doing the heavy lifting in JPD but may have some input to a field or two.  I think creators should me more limited to admin type users and contributors can create and edit ideas.  This is a great product but quickly becomes expensive especially if your org is using multiple Atlassian products.

[Alex Tsai]

Agree. Charge creators and admin but if you want JPD to get usage and grow allow contributors to not just be able to create ideas but give them the ability to edit their ideas. 

[Eugen Stolin]

The current pricing model for JPD works well for us! The main advantages with JPD is that I can have all the stakeholders in the project for free without having them in JS. And tbh, I don't want them in the JS at all. At the same time we don't want all developers to be creators in JPD. So there are only Product managers and owners who are creators with licenses. The rest of users are contributors. 

The one thing, that I have mentioned earlier, is that contributors should be able to see more information in the delivery tab without having a JS or JWM licenses. As it is now, it's just empty for them, even when the work is ongoing. 

[Tanguy Crusson]

Hi @Eugen Stolin , I checked with the team, and as of literally 5 minutes ago everyone should see the delivery progress bar now (but not the list of tickets - that, we won't be able to do without a Jira Software license). Can you please check?

[Tanguy Crusson]

sorry, I spoke too fast: for now contributors without a Jira Software license can see the delivery progress/status fields if they're in the view, not in the delivery tab in an idea yet (that's coming soon)

[Eugen Stolin]

Good news! 

I can confirm that in the view both the delivery status and the progress bar are working! 🙌

Waiting for the tab next! 🙋‍♂️

[Tom Haapanen]

I'm 100% with @Eugen Stolin on this. $100/year for a smallish number of creators (we have 10 licences, as compared to our 300 Jira and 100 JSM) is quite reasonable. Just need to address the gaps so that it's useful for the contributors.

[Alex Tsai]

If you have users paying for JPD and JS then it's not worth it. It should be discounted if you are both a JPD creator and a JS user.

[Tom Haapanen]

There is no discount for using both Jira+JSM, either. In the end, you need to evaluate whether there is enough value in these products to pay the prices set by Atlassian.

We committed to Jira, JSM and JPD and we're willing to pay the licence fees for all three (but not for all users). In contrast, we migrated our old Confluence server to SharePoint instead as there was little incremental value for us there (and we're already using Microsoft 365).