You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hello. We just migrated to a team-managed Jira Work Management board.
We are using Forms to generate issues from Stakeholders.
Some other post shows that it can be "hidden from the customer portal" but I guess we use a different version of the software because I don't have that option.
Ultimately though, the issue type is fine, all I care about is the Form
Hi @Maurice Summers,
Welcome to Atlassian Community!
There is no way around it that the summary field has to be on the form, summary is a system field and will always be required. What you could do is change the name on the form to something else like this:
The posts that you have seen where summary is hidden only applies to Jira Service Management, where you can hide fields on the request form by giving them a default value.
I get that you don't work for Atlassian and you're just trying to be helpful. So I came back up to the top of this comment to say in a more reasonable tone. I appreciate you, I really do.
High, excuse the negativity but this is bad software.
Can you please explain the nature of this requirement?
Why is this only available in Service Management, but not Work Management?
What could possibly be the fundamental difference between managing work and managing service that makes it fundamentally unreasonable to require "work requests" to have a summary (on the Form), but "service requests" need no such thing? What possible benefit could be gained from explicitly restricting the ways I can tailor the forms?
This seems like a simple feature request that causes a lot of pain for a lot of users over a lot of years.
In a less rhetorical way, am I being unreasonable here? Because I am flabbergasted.
It appears Jira's software lacks the feature I need at this time.
For posterity sake I'm exploring two workarounds:
My first option is to make the Form overly complicated..
My other option is abandon Jira Forms and use Microsoft Forms, then use Power Automate to make Jira's.