要約

There are a couple of things regarding billing that you need to be aware of as a site admin when adding Jira Product Discovery Free or Standard that are not intuitive. This page is intended to help you avoid any surprises when you are adding JPD for the first time!

ソリューション

If you are on the Standard edition, check that you have added payment details for Jira Product Discovery

Atlassian is currently rolling out a new billing engine and the migration is not complete: in some sites, Jira Product Discovery is on a different billing engine than other Atlassian products and you need to add payment details specifically for Jira Product Discovery. If you don't do that, at the end of the trial period for the standard plan your plan will be cancelled automatically, and users won't be able to access the product. 

For more detailed information on this, take a look at Jira Product Discovery is coming out of beta, and what that means for billing.

How users are billed by default when you add Jira Product Discovery

If you moved to the free or standard edition on or after 19th July 2023 the next two steps should not be necessary

Site admins will count as billable users by default. Here's how to change that!

If you just added Jira Product Discovery to your site, you'll notice that all site administrators have been given product access to the product and therefore consume a license. This is because whenever a site administrator adds a new Atlassian product to a site, the site-admins user group is automatically given access to the new product. 

You can free up these licenses by removing access to Jira Product Discovery from the site-admins user group. You can then give product access to the people (probably product managers) who will be using the product. For detailed steps, you can view this video on removing product access for admins.

Trusted users will count as billable users by default

Trusted users (a deprecated user experience) will also use a license for all products on site. The only workaround in this case is to change the user's role to either basic or site-admin (after removing product access from the site-admins group).

Managing users in Jira Product Discovery

If the number of users in the "Billing" section in admin.atlassian.com does not match the number of Creators you expect to have

The Check out this video that explains how to check who is getting billed for Jira Product Discovery and common reasons why that number is higher than you expect (and how to fix that). You can find more information about how Creators and Contributors work in The different types of users in Jira Product Discovery, but in short:

• Creators can do everything. They need product access to Jira Product Discovery (i.e. a license)

  
  

• Contributors do not need a Jira license, just a (free) Atlassian account added to the site. They can open Jira Product Discovery projects in read-only mode and contribute with comments and votes, add insights and propose ideas. 

How do I add contributors to a Jira Product Discovery project if they don't have a Jira license? 

You can add contributors without a Jira license by adding them to a specific user group. For detailed steps, you can view this video on adding users to collaborate in a JPD project.

If you started using Jira Product Discovery during beta, you'll first need to create the Contributors user group.

If the feature is turned on for them, Contributors are able to create ideas in a Jira Product Discovery project via a configurable form, but not edit them. For detailed steps, you can read this post on Letting contributors create ideas in a Jira Product Discovery project

What's the difference between product roles and project roles?

An additional aspect to understand is Product role vs Project role:

• Product role: Is the user a Creator or a Contributor in this site? (i.e. Do they have a Jira Product Discovery license or not?) As mentioned above, creators need a JPD license, contributors do not

• Project role: project roles define a list of permissions in a project. When users are given a project role in a project, it limits the list of features they can access in this project. Users can have different project roles in different projects. This video on JPD project roles and project access explains this in more detail