nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can I turn off creating new ideas from list view?

Glenn A

I would LOVE to remove the ability to display the "Create new idea" button that appears above the table on list view pages. In fact, I would love for the only way to create an idea to be the "Create" button in the top navigation bar/menu (so, also disabling the "+" button at the top of the list view table).

Ultimately, what is driving this is that even though I have templated how my "new ideas" look, this template new issue is only reachable if you create new ideas from the nav/menu. (I really don't want/trust my people to fill out exactly what I want how I want if it's not presented to them up front.)

Thanks!

Accepted answers

Tanguy Crusson

@Glenn A

For this purpose we usually recommend you give everyone "contributor" access to the project: all they'll see is the top-level "Create" button.

That's typically in the use case where you want to let people from across the company to create ideas (leadership, stakeholders, etc.).

If you want to make sure every creator on the project can only create ideas via the form, there's currently no way to enforce it.

All comments

Sarah Schmitt-Bär _Seibert Group_

I’m not aware of a way to remove this button. Personally, I find it super helpful as a quick shortcut for adding new ideas without needing to fill out all the details right away. 😊

Whenever someone submits a new idea, I get a notification, which lets me jump in and add more information if it’s available. I imagine that if adding more context was required upfront, some people might hesitate to share their ideas. For me, it’s all about gathering everything and sorting out the details later!

Tanguy Crusson

@Glenn A

For this purpose we usually recommend you give everyone "contributor" access to the project: all they'll see is the top-level "Create" button.

That's typically in the use case where you want to let people from across the company to create ideas (leadership, stakeholders, etc.).

If you want to make sure every creator on the project can only create ideas via the form, there's currently no way to enforce it.

Glenn A

@Tanguy Crusson, OK, noted, that is unfortunate... as much as I'd love to keep my set of direct users limited to just contributor, the fact that they cannot edit existing tickets with that level of access makes it all (creator) or nothing (contributor).

My use case is as follows:

user x creates an idea in JPD and is assigned to it.

user y as the SME has to refine the idea. if user y is only a contributor, then that is not possible.

Tanguy Crusson

Thank you @Glenn A - we're currently looking at how to improve idea creation workflows so this is timely

Isabella Moon

The more I'm researching this issue the more I have the impression most Product Managers (like me) would like some ways to:

Allow people from other teams (e.g. market facing teams like Sales and Marketing) to provide feedback directly in my PMs Product Discovery Project.
- Allows me to have all my work in one place without needing to cross-match it akwardly from some queue
- Allows me to link delivery tickets from my dev team for live progress and timelime information which is the main USP
I want the feedbackers to be able to:
- create and idea from a form I set the template for with custom choice of fields being mandatory or not (not all fields or none like right now)
- edit and delete their idea
- create, edit and delte their own comments, votes and insights
- edit fields I chose: for example, I want the sales team to be able to workshop together the priorities of their own topics, so I want them to be able to edit the one field "SL Prio"
I want feedbackers not to be able to:
- see all ideas
- see all views
- see all sections
I want to determine:
- how they can provide feedback: form only, top create button, create button in each view they have access to
- what ideas they can see (e.g. via field criteria)
- what views they have access to/ show up in their menu
- what sections they have access to/ show up in their menu
- Ideally, I can determine this via roles (Sales Team, Customer Support Team, C-Level team, etc.) and/or field settings (allow/don't allow role xyz to use)
I don't want to have to create a service management queue system that doesn't provide the great insights I can share with my feedbackers directly
As a PM I want to additionally share "view only" views to my feedbackers about roadmap and their feedback's processing status, so they don't need to always ask me, how far along their feedback has come
Ideally: I can create a form for external users only to give customers, end users, investors etc. a way to give me ideas/feedback, but no access to the project.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

template

issue-create

jpd