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
TLDR: History
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!
Thanks.
This Brings me to the second question: Can I change its name?
The reason is that If I create a custom field with the same name I never know which one is the one I need (for example when editing a screen or a field configuration)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Oh, and one more question:
What is MOBO, MOFT, TBO ...
And, UAT is an environment?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic Brough -Adaptavist- , I am unfamiliar with this field. Can you point me to it? I understand the concept of the field and have used similar in other products but have never run across this in Jira cloud.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@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"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This explanation of how to replace it might be useful:
You can add a custom field (field type: Select List) for this. Then configure your screens, so that you remove the out-of-the-box 'Environment' field and replace it with your custom field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Hadas Hamerovv ,
I am not familiar with the environment field. Is it possible that this is a custom field that an admin created? What type of project is this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This official documentation explains:
Environment is a system field, it's free-text and used to register information about the environment from where the ticket was generated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.