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; } } }

Two "Create" Buttons: Disable the lower one?

Katrin Erhardt

Hello Community,

Is there a way to disable the lower "Create" button" in JPD? Our goal is to ensure that users with a Creator license can only submit new ideas using the upper "Create" button, which opens the input form with all mandatory fields.

Currently, the lower button allows submissions without filling in required fields, and we want to enforce the complete form submission process.

Has anyone found a solution or workaround for this?

Thank you in advance!

Accepted answers

Tanguy Crusson

Hi @Katrin Erhardt , it's not possible to turn it off today - there are a few different parts of the UI where creators can create ideas inline.

Can you please tell us more about why you need this? Thanks!

All comments

Tanguy Crusson

Hi @Katrin Erhardt , it's not possible to turn it off today - there are a few different parts of the UI where creators can create ideas inline.

Can you please tell us more about why you need this? Thanks!

Katrin Erhardt

Hi @Tanguy Crusson

thank you for your super fast reply!

We use JPD for submitting ideas for IT projects from the business departments.
We have created a form with predefined mandatory fields to ensure that the business submits sufficiently detailed requirements, so that the ideas can be properly evaluated and prioritized by IT.

The business users have a Creator license because we want to ensure that the idea can be edited later on (as far as I understand, this is not possible with a Contributor license).

Now, we want to prevent the inline Create button from being used, because otherwise the form with mandatory fields would be pointless.

Or am I overlooking a better solution?

Tanguy Crusson

That makes sense, thank you. Would you want this experience (disabling inline creation for ideas) to apply to everyone including IT, or just business people? Do you use a single project where the business suggests ideas and IT prioritizes them or do you have one project for intake processes, and one for prioritization?

Katrin Erhardt

Hi @Tanguy Crusson ,

there is only one project: The business departments submit their ideas/requirements. After submission, business evaluates the ideas using a scoring model. Subsequently, IT also evaluates the ideas with its own scoring model, and a rough effort estimation is made for all involved IT teams.

From this, an overall prioritization is determined, which feeds into the timeline planning on the roadmap. Once an idea is approved as a project, it is handed over to Jira as a ticket (Epic).

Business and IT users have Creator licenses, while Portfolio Managers have Admin licenses. IT does not create own ideas (at the moment) so for them the Create button is irrelevant right now.

We have just started implementing this new process and are very open to adjustments—for example, splitting into multiple JPD projects if that proves beneficial.

daniel_jones_58rpy9

+1 for this feature.

We've found users are using the lower Create button, which then misses crucial information in our process, being submitted at initial idea creation using the upper Create button and form.

André_or9czx

Let me add another, but related concern. We have a field which we check in our workflow if it exists. But the inline creation in a timeline view doesn't show that field, which leads to an error to the user who can't even add the field. So I would like to have the option to either have the inline create buttons (I mean the "plus" in the timeline view) show the actual modals which are also behind the "upper" create or to not show at all to prevent this weird behaviour. Any tips on how we could do this now would be appreciated too