The default type "Ideas" needs to be configurable - we're using JPD for much more than this now

[Matthew Stedman]

Please allow us to either:

1. Limit selection of "types" in newly created JPD items AND/OR
2. Rename the "Ideas" type.

The default type "Ideas" cannot be renamed.

You can create additional types...but there is no way to hide the "Ideas" type as a selectable option whne you CREATE new JPD items.

Managing of Ideas was a great motivation for building this..but the concept is so valuable to many other things additional to idea.  Forcing "Ideas" to exist ...confuses our users.

Effectively we think JPD is the best answer from Atlassian so far for forcing business people to document their needs upfront/enough for technical teams to "High level effort estimate" against BEFORE Business asks are allowed to get anywhere need a "Backlog".

It allows business teams to agree amongst themselves what's most valueable before items distract technical teams from their work.

We are using it for new Enterprise Reporting Features.

If forces all the documentation, visual proof of concepts and back and forth prioritisation to occur before its allowed to then be linked to an Epic (DashboardName_Version) in backlog within out Software Delivery JIRA's.   Then we deliver, and copy the documenttion into Confluence for those things that actually get delivered - keeping our Confluence clean.

Please consider the abiliyt to limit what "types" can be selected when creating new JPD items.

[Walter Buggenhout · Accepted solution]

Hi @Matthew Stedman,

The capability to create custom types (and model them into a hierarchy) is already available as an open beta with the JPD premium plan, which was launched some time ago. You can read more about the specific feature in this Community Article.

Hope this helps!