Atlassian Team members are employees working across the company in a wide variety of roles.
March 2, 2023 edited
All of this - your question and others in previous messages - I'll share in a subsequent article. We have a lot of pieces that have landed already and we're still trying to validate the final ones before we can share the details as to how this all fits together.
Don't worry you'll have ample time to move from the beta edition to the free/standard edition.
Hi @Tanguy Crusson , I hope you are considering the create issue dialog as a form :)
Contributors must be able to contribute ideas from Jira. The Chrome plugin doesn't allow for a form and not every company uses Slack. And really what is the point of breaking the workflow and forcing users to work from outside of Jira especially if they are used to work with Jira?
Atlassian Team members are employees working across the company in a wide variety of roles.
March 2, 2023 edited
> And really what is the point of breaking the workflow and forcing users to work from outside of Jira especially if they are used to work with Jira?
I never said we would. I just said we would share more details in a subsequent article. Please bear with us, we'll get there, and in the meantime you can enjoy the free beta product 🙂
Hi @Tanguy Crusson you had literally admitted 2 messages ago that the contributors will be able to add insights, comments, votes and reactions after submitting the ideas. Is "not being able to edit ideas" conflicts with this or are we getting it wrong?
@Tanguy Crusson Thanks for the update! Assuming the new changes to Contributor will be configurable as we will not want contributors submitting ideas? We were one of the ones that liked the other version. If configurable, will it be configurable at a user or group level? i.e. engineering managers can submit ideas via Slack but Operations team cannot.
We are evaluating Product Discovery and there are a lot of things I really like about it. But how contributers can submit ideas is a really essential question for us. If you could shed some light on what this means:
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.
Atlassian Team members are employees working across the company in a wide variety of roles.
March 29, 2023 edited
@Peter Dimopoulos it depends on what you want administrators to do: if it's just create projects and manage access, then no. If admins want to create fields/views/ideas/insights, then they need a license. Details in the link that @Bill Sheboy shared.
Please find the below questions for miquido.atlassian.net:
a) we have more than 10 Site Admins and Org & Site Admins (combined number) > since we joined JPD (for testing purposes), all of them have been automatically added to JPD > question: are those users billable from your perspective? (context: they haven't signed up for JPD, and they won't be using JPD)
b) Creators / Contributors per project or organization?
example - if we want to: - run 10 projects at JPD (each of them has a separate project at Jira Software and a separate team) AND - use all JPD projects under Free Plan, are we limited to 3 creators across all projects? OR are we limited to 3 creators per project?
a) Everyone who is given product access to Jira Product Discovery (in admin.atlassian.com / Directory) is going to be billed for JPD. If they won't use JPD, just remove product access and they won't be charged.
b) the limit of 3 creators is for the site, across all projects
121 comments