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

Required internal fields

Sarah Lincoln

We need certain fields Mandatory but they are only ever to be filled in by an internal service desk agent, not the customer. For example, we must fill in the Tempo Account field before the item is closed. The tempo account field will not be filled in by the customer but needs to be mandatory before an internal agent can close the ticket. We also need to do the same sort of thing for a custom field.

Accepted answers

All comments

Steven F Behnke

Outside of Service Desk, there are two options.

You can make fields required always, by marking them as required on a Field Configuration.
You can make fields required during a transition screen, by using a Validator (provided by a plugin such as JIRA Suite Utilities or Misc Workflow Extensions).

Sarah Lincoln

Making them always required would mean the customer would have to fill it out before they could submit their ticket, which we don't want them to fill out.

Unfortunately setting the Tempo Account field to required on Transition doesn't work as Tempo uses a default account of 'None' so the transition thinks the Account field has a value in it and doesn't stop the transition sad

Steven F Behnke

Are you on Cloud or Server? What add-ons do you have to augment workflow functions (JSUtil, Misc Workflow Extensions, Script Runner, etc)

Sarah Lincoln

We are on Server

JIRA Misc Workflow Extensions

Adaptavist ScriptRunner for JIRA

If I could somehow empty the Account field, at least then I could set the Account to Mandatory on the very last transition and it would work because JIRA would think it was actually empty.