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

How to make description mandatory in team-managed projects?

Torsten Lenhart

In team-managed projects, I can make fields mandatory by ticking the "Required" box under Project Settings > Issue Types.

However, this seems to work only for fields I have added and not for standard fields like "description". The checkbox is greyed out in this case:

Screenshot 2023-04-12 165040.png

My question: Is there another way to make "description" mandatory? Thanks!

Accepted answers

All comments

Trudy P Claspill

Hello @Torsten Lenhart

What problem are you trying to solve by requiring data in the Description field?

You could set up a Rule on every transition to require data in the Description field. Unfortunately that rule can't be added to the Create transition, so new issues could be created with no Description. They just couldn't be changed to any other status if you added the rule to every other transition.

You could have an Automation Rule run to check each newly created issue for Description content, and email somebody if one is created without information.

You could also add a Custom Paragraph field, call it something like Required Description, and make that field Required. You can't remove the original Description field though, so it might be confusing having the two fields.

Edrick

This is a lazy answer. It will just be easier to allow administrators to make the field required

Trudy P Claspill

@Edrick

How is this answer "lazy"?

Given that what the user wants to do is not supported, I have thoughtfully provided 3 alternatives?

Please note that I am just another user of the Atlassian products. I am not an Atlassian employee. I have no input or control over changing the functionality of the product.

Edrick

its lazy because the correct approach to deal with the request, is to allow administrators to make the field required. Any other approach is just a workaround.

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-software

jira-software-cloud