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

Pre-Established Defined Ticket Fields

scott_x3ogpw

In creating a project board for future tickets, is it possible to create quality checks around the tickets, specifically to the point of creating a form and only allowing a ticket to be submitted when pre-populated fields have been included (nothing more, nothing less)? Thank you!

Accepted answers

Dave Rosenlund (Trundl)

Hi, @scott. Welcome to the community 👋

Maybe you can tell us why you think a form is the right answer to your issue?

Jira admins. can create or customize issue screens to include only the fields you want and/or make some or all fields required. Wouldn't that do the trick for you?

See this post and the answer by @Ste Wright for the details.

How to design the the "create new issue" screen?

I hope this helps,

-dave

All comments

Dave Rosenlund (Trundl)

Hi, @scott. Welcome to the community 👋

Maybe you can tell us why you think a form is the right answer to your issue?

Jira admins. can create or customize issue screens to include only the fields you want and/or make some or all fields required. Wouldn't that do the trick for you?

See this post and the answer by @Ste Wright for the details.

How to design the the "create new issue" screen?

I hope this helps,

-dave

scott_x3ogpw

Thanks for getting back to me so promptly, @Dave Rosenlund _Trundl_! What you tagged sounds like it could do the trick for me. Can I establish such fields on a per-project basis? In other words, my goal is to create a specific project and within it only allow an "issue" to be submitted when specific fields within are completed. Any help is appreciated!

scott_x3ogpw

Just checking in to see if you have any additional thoughts here @Dave Rosenlund _Trundl_ Thanks in advance!

Dave Rosenlund (Trundl)

Hi, @scott. I'm sorry that I missed your first reply.

There are some hacks I've seen people do, but I would advise against them. It's far better to live with the Jira capabilities that you're given and customize things with the available options.

A simple hack that isn't too crazy would be to create new issue types—e.g., Tasks, Bugs, etc.,—at the Story level. Keep the number to a minimum, but then you can create different create screens for each new issue type at the story level. That way non-devs can have Tasks while devs have Stories and QA has Bugs, for example.

For other, more sensible per-project customizations, Atlassian created "team managed" projects (vs. company-managed). But with team-managed projects only certain things can be customized on the team level. The create screen is not one of them.

Read up on that Team vs. Company topic -- it may get you to where you need to and keep your number of custom issue types to a minimum.

-dave

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud