To me it is more intuitive to have a dropdown list but before creating a custom field and dismissing this system field I would want to verify that I am not missing something
Jira 1 had a need to capture environment details, but no way to do it usefully with a custom field, so Scott and Mike put in a free-text field to prompt people to tell them about the environment the issue had been found in.
You're absolutely right in that it's more intuitive to have a drop-down. The first two custom fields I ever added to Jira were a pair of "Tell me which environment you're looking at" fields. One said "MOBO, MOFT, TBO or other", and the other was "Prod, UAT, dev 1, dev 2, dev 3.... etc".
So, you're not missing anything. The "system" environment field is mostly a hangover and if you have no use for a free text field called environment, just ignore it. It's the only system field that doesn't have any special functions or quirks attached!
@Jack Brickey - yep, it's a system field, so it's company-managed projects based. That means you don't see it on the list of custom fields, but you can add it to screens and set it's renderer, make it mandatory or hide it in the field configurations.
I don't think I've seen it used in any of the project templates for a while, so it's something we have to go add if we want it.
@Hadas Hamerovv - those were the names of systems I did support and development, and eventually because the (technical) owner of, <mumble> years ago. UAT is a common acronym for "User Acceptance Test"
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event