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

Make field required for users within a group with Automation

Alexandria (Lexi) Codd

I currently use a plugin to accomplish this within the workflow transition validators. However, this is cumbersome to add and manage, as the configuration is buried within all workflows. I want to go to one place, I was thinking of automation, adding a single rule for particular projects that if a user in our "cid" group creates an issue, then they are required to fill in specific fields. I couldn't find a field a "field required" action in the automation dialog or in the documentation though, am I blind, or is this not an option?

Accepted answers

Maciej Dudziak _Forgappify_

Hi @Alexandria (Lexi) Codd

If you're interested in alternatives to validators and are open to using an app, our team has developed Field Rules - UI Modifications for Jira.

In one place, you can create a UI Modification—a list of rules applied to a selected context, defined by a project, issue types, and view type (1000 context per a modification is allowed). Among the supported rules is the "Make a field required" rule, which can be applied to the Global Issue Create view.

This is made possible by the latest UIM API for Forge apps, though some limitations still apply and here’s an example of how it looks:

And the "Make field required" rule:

I would appreciate it if you could give it a try.

Cheers

All comments

Victor Law - Ricksoft

Hi @Alexandria (Lexi) Codd

I don’t believe there is a way to use Jira Automation to enforce required fields. Automation typically triggers after an event or action has occurred. Therefore, it doesn't seem reasonable for Automation to prevent a user from creating or editing an issue if a specific field needs to be required.

It is only possible to have Automation to check if a field has value after an issue is edited or created and add a comment to remind the user.

Hope this helps.

Thank you.

Alexandria (Lexi) Codd

yeah, i know theres a work around or two out there for things like clearing a field if a particular user edits it and was hoping there may be slick way to get the same desired outcome for requiring a field