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.
June 23, 2023 edited
Hi @CC , it should hopefully get there in the next week. (create experience for creators)
> I would like to add to your list, allowing contributors to edit their own creations.
I don't think that's going to happen. That's literally the only meaningful difference between creators and contributors. If we added that it would be the equivalent of just shipping a free product 🙂 Gotta pay the bills!
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.
June 23, 2023 edited
@Jeny Stoeva we'll look at it when we revisit the contributor experience. For now this hasn't come up that often in user feedback. But I'm sure we'll get to it later.
We're focusing our efforts on the sharing / stakeholders experience instead at the moment.
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.
@Tanguy Crusson Super, super, super excited about the creator experience.
Apologies for not being clear, I only want the contributors to be able to edit data they are allowed to enter. For example, the description (which is based on the template) and the required fields.
For example, I am able to edit the comment I just made with greater detail.
Atlassian Team members are employees working across the company in a wide variety of roles.
June 23, 2023 edited
Gotcha thanks @CC - today in the Jira permission model it's kind of 0 or 1: either you can edit all fields or you can edit none, which makes things like this relatively complex to implement. We'll consider this feedback for future iterations.
Also, are there any plans to make insights independent of ideas? I believe this would be a better solution than allowing contributors to create ideas - we would end up with a massive backlog of unprocessed ideas (even with the ability to merge ideas). If insights are an independent entity, then contributors could submit Insights that are processed separately and then tied to ideas.
I already merged ideas and it is a great feature. It is an option in the dropdown in the 3 dots in the top corner (when the idea is opened in the side panel). And a separate button in the top corner when you have opened the idea on a full screen.
Hi @Tanguy Crusson May I know if it's possible for Contributors to edit the ideas that they submitted after submission? I'm currently on beta and can see that it's not possible for now, wondering if that will change in the Standard version?
@Tanguy Crusson I've scoured the last three pages which seem to be the latest comments to this page, but haven't seen a request to be able to
Only share specific views to contributors
What is it?
When using this for both idea collection & product discovery, it would be great to be able to select specific views in the JPD that is made available to contributors either by named user or user group rather than them having access to all views automatically.
Why is this important?
In this case, I want to create a view titled "Ideas portal" and allow all contributors to be able to submit and idea, then vote on the rest of the ideas. A hack I guess for the other requests about a full on ideas portal like Aha! provide.
Even if I were to restrict a view to show only ideas that e.g. have been triaged by product for voting, contributors can still click on another view and see the full list.
Limit field visibility to contributors
What is it?
When using this for both idea collection & product discovery, it would be great to be able to select which fields are "public" to contributors vs which fields are "private" to creators and/or a user group like engineers.
Why is this important?
I believe currently if you have the previously mentioned ideas portal as a separate view. If a user clicks on the idea, the full set of field values are visible in the ideas details panel that opens. Working in the same JPD as a product manager that your users are submitting ideas, I don't want user contributors to see our work in progress, description, notes, etc. I want to be able to choose which fields are visible not only in the table, but also when the issue is clicked on by a contributor for more details.
Great product @Tanguy Crusson To collect issues in Jira SW we use a collector and embed the url like https:// <mycompany>.atlassian.net/jira/secure/CreateIssue.jspa?pid<####>&issuetype<####> in confluence and sharepoint so users go directly to the form. How is this done in Jira Product Discovery?
I have configured the "create idea" to use a custom "submit ideas here" view and it works great when the create button is clicked in the UI. When i use the PID and Issuetype in the above format it launches the create idea but it contains every field in the project instead of the custom "submit ideas here". Is it possible to have a URL that pulls the correct form? thanks Patrick
@Tanguy Crusson thanks for the response. For creating issues in Jira Software we use the URL that takes us straight to the create issue form https:// <mycompany>.atlassian.net/jira/secure/CreateIssue.jspa?pid<####>&issuetype<####> where PID is the project ID and issuteype # indicates what type (epic, story, bug, etc) I used the PID and Issuetype for my Product Discovery project and Idea and it did bring up a form but it looked to contain every field in the system and json - not the customized form that i set in the project settings for the create button Portion shown below
Create issue
Project: GDII Idea Intake
Issue: TypeIdea
Summary Required
Description, Preview descriptionLinked Issuesautomatesis automated byBig Rock Item Big Rockblocksis blocked by Discovered while testingTesting discoveredclones is cloned bycreated created by is a duplicate ofis duplicated byhas to be finished withhas to be done beforehas to be done afterIs Implemented byImplementsFrom InitiativeTo Initiativesplit tosplit fromis parent ofis child ofis idea foradded to ideaimplementsis implemented bymerged frommerged intocausesis caused byrefers tois referred to byaffectsis affected byrelates toSF-depends onis SF-depended bySS-depends onis SS-depended byis a dependent sub-projecthas dependent sub-projectsupersedesis superseded byteststested byverifiesis verified byIssue
Begin typing to search for issues to link. If you leave it blank, no link will be made.
AssigneePatrick Blackburn Unassigned Automatic
Reporter RequiredPatrick Blackburn
Start typing to get a list of possible matches.
Priority
P0 - Highest P1 - High P2 - Medium P3 - Low P4 - Lowest
Labels
Begin typing to find and create labels or press down to select a suggested label.
Project target
Once an idea has been selected and prioritized you can plan its delivery. This field represents when delivery work aims to complete.
Hi! Is this feature (allowing Contributors add Ideas) widely available or still in beta testing (for some accounts)? I activated it at Settings/Features/Create_ideas but my Contributors still can't see the Create button. When I try it through "Preview in project" I don't see it neither.
EDIT: Solved. I was looking for the wrong Create button. There is one for Contributors and that's seems just enough :)
Feature request please: As a... contributor who is less experienced with JPD projects, When... I follow a shared "Create Idea" link, I want... the "Create an Idea" form to be displayed automatically, So that... I can submit my idea easily - even with limited familiarity and understanding.
Context: We're a retail enterprise (20k+) with numerous outlets across the country under different brand names. A significant number of our Atlassian-Jira users are not well-versed in Jira. In an effort to migrate 'ideas' from Google Forms to JPD, our customers frequently find it challenging to adapt to the new step of not being directed immediately to a submission form upon clicking the link.
Question: Is the billing/pricing based on "product access" roles or "role" roles? We do have some team members that are "Creators" in product access, but "Contributor" in role (see screenshot).
Also: It seems that JPD just switched some of our contributors to creators. We initially only had 3 creators to stay in the free tier, but JPD automatically changed the product access to creator for 2 of our contributors. Is that a known bug or somehow related to letting contributors create ideas?
Product role = does someone have a license or not? (product access = true)
Project role = what's the set of permissions for them in the project. It's capped by product role (as in: if someone doesn't have a license but you give them creator project role, they will only be able to use permissions that a contributor can use)
On your other issue: there's nothing JPD can do to grant users product access. It's likely that there is a user group that has been given JPD product access (e.g. the site-admins user group), and any time you add users to this group they automatically get product access
Contributors should be able to edit the ideas that they created. It is very common for someone to want to edit something they wrote. Please update your role permissions logic to allow contributors to edit their own ideas.
147 comments