Project

General

Profile

Actions

Defect #39058

closed

Custom field required on one tracker applies to all trackers

Added by Jon Schell 7 months ago. Updated 7 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Custom fields
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

Description

Adding a custom field to multiple trackers and I want it to be required for one of them, but there's only a global checkbox.


Files

Capture.PNG (33.8 KB) Capture.PNG Jon Schell, 2023-09-13 18:18
Actions #1

Updated by Go MAEDA 7 months ago

Could you describe the problem in more detail? It would be even more helpful if you could attach screenshots.

Actions #2

Updated by Jon Schell 7 months ago

A custom field only has a single checkbox to make the field required. But I want the field to only be required on one tracker, say Bug, and optional on others, like Action Item. And you can't have two custom fields with the same name, so I'd need to have some weird looking name for one or both if I was to create two custom fields instead.

I suppose it's more of a feature request than a defect, but I consider it a deficit.

Actions #3

Updated by Holger Just 7 months ago

  • Status changed from New to Closed

You can define granular rules to make some fields (including custom fields) required per tracker, issue status, and role of the user editing the issue. This can be configured in Administration -> Workflows -> Field permissions.

For that to work, you would enable the custom field on the desired trackers but not mark it universally required. Then, in the workflow field permissions screen, you can mark it as required for the desired trackers / roles / statuses. Note that if a user has multiple roles in a project, Redmine uses the most "open" permissions applicable. Thus, if any of the user's roles in the project allows the field to be unset, it will not be required to be set for this user. Administrators are assumed to have ALL roles (including Anonymous and Non-member) in a project when deciding which fields they have to fill.

Actions

Also available in: Atom PDF