Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Templates not available from issue creation in top menu bar

If I'm in the JPD project and I click the blue "Create" button at the top of the web page, I do not have the option for a user to specify a template.  The only way to specify a template is to create the issue, then open the issue and click on description.

This is the reason why my issue submitters are not using our description template.  


4 answers

1 accepted

Suggest an answer

Log in or Sign up to answer
3 votes
Answer accepted

This is most likely a limitation since the Create button at the top is for all of Jira and this product isn't really using the "regular Jira stuff".  

1 vote
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 29, 2022

Hi @Seth Mason

Thank you for sharing this feedback with us. Indeed, it's a limitation that we have, where the "create" button in the header is not specific to the Jira Product Discovery., and templates can't be applied from there.

I passed this feedback to the team. 


Ditto on the Qs

I'd like to require certain fields be populated at idea creation.  I love the oneliner but it does require the user to go into the idea twice to update the details.

Also, I'd like to default a template.  I love, love, love the templates and wish the software projects had the same functionality.

I have the same issue. The templates are great to enforce custom headers so people write up tickets in a standardised manner but this limitation circumvents that.

In line with the choice of custom fields on show in the creation screen, I would like to be able to present users the minimum criteria they need to start a ticket so I can avoid chasing them / cleaning stuff up myself. 

AUG Leaders

Atlassian Community Events