Hi @Tanguy Crusson for the article and video, I find them super helpful.
I have a question regarding the form to submit ideas that you showed during the later part of the video. How will the info on the form map to the fields we customize on the Ideas Board?
i.e Let's say we have the same fields on the submit form and on the ideas board on Jira such as Client name, Goal, Type of ideas etc. Ideally we want to automatically map those fields submitted on the form to the fields available on the ideas board to save time for people who review the ideas submitted. May I confirm that it's possible?
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.
I have a couple of other questions regarding licensing and permissions:
Who (i.e. which Jira roles) can add Creators, Contributors, and Stakeholders, or change existing roles for a JPD project?
Where will this happen in the product: in JPD project settings or in the Site Admin, user management area?
If Creators can do this from inside of the JPD project (as they do during the beta today), this could have serious consequences: a single JPD project now appears to become point-of-sale, with potentially large impacts to licensing costs for a customer.
Atlassian Team members are employees working across the company in a wide variety of roles.
March 23, 2023 edited
@Bill Sheboy great question. Rest assured, we've respected Jira's current model for that:
A site administrator needs to add users to the site's user base, and decides who gets product access vs not (creators vs contributors, who pays vs not). In the site admin section.
From that point onward, once they're in the site and with/without product access, creators can invite these users to work with them in Discovery projects, as creators or contributors.
There are cases where a site admin might decide to let users invite other users (there are options like this in the site admin section). This would work for JPD too, if you decide to do that.
Hi @Tanguy Crusson You say 'right now, you need a Jira license to be a contributor' and 'when we ship that you'll just need an Atlassian account and be part of the site's user base'. Wouldn't you need a licence in order to have an account anyway?
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.
Site admin (or above) adds/edits user access for JPD, selecting Creator or Contributor level
And then...Within a specific JPD project...
A Creator can add/edit users...up to the level they are configured as a base user (Creator or Contributor) AND no higher (e.g., a Contributor-base user, cannot be made a Creator in a project)
Atlassian Team members are employees working across the company in a wide variety of roles.
March 23, 2023 edited
No worries at all @David Griffin , it can take a while to wrap your head around the Atlassian identity and licensing model 😅
Here are the basics:
Anyone with an email address can go to id.atlassian.com and create an Atlassian Account, which they can use to log in to Atlassian sites (xyz.atlassian.net)
On these sites, administrators can add products (Jira Software, JPD, Confluence, etc.). They can also add users (in effect what they do is add these people's Atlassian Accounts to the site user base
Up until now, no one paid for anything. The Atlassian Account is free, adding it to a site is free
Then, an admin can give product access to a user on the site. For example: access to Jira Software, access to Confluence, access to Jira Product Discovery. That may be a free or paid operation depending on the edition of the product (e.g. JPD has 3 free creators, which means "on the JPD free edition you can give JPD product access to 3 users for free")
What we're implementing right now is a way for users with an Atlassian account, and added to the site, but without product access to JPD (bullet points 1 and 2 in this list), to be contributors in JPD. So, contributors in JPD, for free.
Help me confirm pricing. I have smaller company with 90 or so users and they all have JIRA, confluence, and Service desk.. My product team only has 5 creators but the remaining 85 will be contributors. So will this increase bill by $50 per month since we only have 5 creators.. That is my understanding now but wanted to make sure..
Is there (or will there) be a way to change the delivery progress to track by story points vs. ticket count?
How does the sorting work for linked delivery tickets - e.g. what determines the order they appear in? I can't seem to find a pattern (it's not how I add them, nor status). Personally I'd love to be able to re-sort at will (like on the main views where you can drag and drop) to help with stack ranking pieces of delivery.
Less a question, more of a suggestion, but it'd be great if you could define a custom time scale for the timelines (we operate in 6 week cycles vs. Quarters for example). It would also be great if we could rename the scale (I'd much rather see Q1 vs. Jan 1 - Mar 31st).
@Tanguy Crusson -- what is the pricing impact of adding a team of people who do not currently use Jira as either Contributors or Stakeholders? Will I need to pay for a base Jira license?
Atlassian Team members are employees working across the company in a wide variety of roles.
March 27, 2023 edited
@Patrice Cantalupo could you post this as a separate question/article in the community group? It's going to be easier to answer there (and keep this one about the pricing and creator/contributor model). Thanks!
@Tanguy Crusson -- getting our new CPO on board with this, which is exciting! One question he/we have is around the customizable forms for idea submission. When will that be available? (Is it in beta now? How are they set up?)
@Tanguy Crusson So, it's not implemented yet, right? I've been trying to connect a user this way by following the example in the video but the user in question is just redirected to the site portal when following a link to the project. I though I was doing something wrong. 🙈 (well, technically I was, but we all know what I mean 😄)
Therefore, the correct solution at the moment is to give the user access to Product Discovery. Is that so?
Atlassian Team members are employees working across the company in a wide variety of roles.
April 5, 2023 edited
@Eugen Stolin that is correct. It's coming very soon.
Don't worry, we'll give you time to clean things up when we launch the free and standard editions, so you can assess who needs creator vs contributor access and make the changes before the first bill comes.
Atlassian Team members are employees working across the company in a wide variety of roles.
April 6, 2023 edited
Hi everyone, the ability for contributors to submit ideas is ready for you to try. Just let us know there and we'll turn it on for you in exchange for some feedback / confirmation that it's working for you:
Thank you for the update! I would like to inquire about the availability of functionalities for submitting ideas as Contributors, specifically through the customizable form. Will these features be included in the General Availability (GA) release or will they be introduced at a later date, similar to the Stakeholder role?
79 comments