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

Using several create ideas templates in one project

Katrin Erhardt

Hello Atlassian Team,

is it possible to use different "create idea templates" in one project?

The background to my question is that we have different classifications of IT project ideas that require different amounts of information from the idea generator depending on their size/relevance. I have not found the possibility to create different templates for different views, or alternatively to set a choice in a template (e.g. you choose the classification and the mandatory fields change depending on it). Can you help me with the best way to solve this?

Thank you in advance & kind regards

Katrin

Accepted answers

Jet_m3qoex

Hi Katrin,

Currently, this feature is not available. However, I've noted it as a potential improvement for future updates. To ensure clarity, could you please advise on how individuals submitting ideas can determine the appropriate form to select?

Additionally, I recommend using Jira Service Management for more customizations in the submit form. JSM offers a customer portal and using automations you can automatically transfer ideas/projects to Jira product discovery to triage them.

You can learn more about that here: Set up a Jira Service Management queue to receive feedback from customers and internal teams (and how to set up automation rules to do it)

All comments

Jet_m3qoex

Hi Katrin,

You can learn more about that here: Set up a Jira Service Management queue to receive feedback from customers and internal teams (and how to set up automation rules to do it)

Katrin Erhardt

Hi Jet,

thank you for your quick response.

In our use case, several departments submit their ideas for the IT project portfolio. Ideas can be classified as "normal" projects, legal projects, projects required by management, procurements, or change requests. The requirement managers who submit the ideas can usually judge for themselves what the idea is about.

The solution via Jira Service Management is clever, thank you. However, it is probably more suitable if the idea generators do not continue to work on or follow up on the ideas themselves afterwards. In our current process (currently in another tool), there is bilateral processing of the idea. The departments are involved in the idea workflow through the requirement manager (who is also the idea generator) for scoring the idea, approval steps, etc.

Thank you in advance and best regards,
Katrin

Lisa McCann

Katrin,

In JPD, I created a field where they can select the idea type and have that part of my default create idea template - for example, a new add-on; existing feature enhancement. I also have an origin field, such as Mandatory/Compliance; Executive, etc.

Katrin Erhardt

Hi Lisa,

thank you very much for your reply! That sounds like a practical solution.
Our wish is to mark different fields as mandatory depending on the selected idea category or to display different fields at all depending on the idea category.
However, as this is currently not possible, we are perhaps thinking too complicated and should simplify our process :-) Thanks for the suggestion!