Maybe this will help:
scroll down to :
In the table, you'll see
>Show list of fields
Open it and there are the standard fields useable by JQL.
If you have the correct permission, Custom Fields are in the "Administration Screen (cogwheel gear icon) > Issues > Custom Fields" on the left side of the screen. Some of the System Fields are on these screen to (take a look at the tabs on the left side again).
I'm not an Admin, but I'm providing feedback to someone who's creating a JIRA project for our bug/suggestion tracking. Some fields I'd like to have are missing and it would be great to view a user guide or equivalent that would list all the fields that can be implemented for a JIRA ticket.
Does such an entity exist?Thanks. Using JIRA Server.
You can define whatever fields you want for Jira issues - that's what custom fields are for.
For a list of the built-in "system" fields, see Richard's link below - there's a table part way down with a line "fields" that expands to show the system fields that are always there (but can be ignored or hidden if you want)
Oh, this is great. Thank you! Now, for the next question. I want to use the TYPE field to record whether this issue is a Bug, Suggestion, etc. How can I find out if it supports a pulldown menu. We need the following values:
Can we define them? Or are the values pre-defined?
What "type" field?
If you mean "issue type", look at, and amend, the project's "issue type scheme"
If you just have a "Type" field, then that is a custom field, and you need to go to Admin -> custom field -> "Type" -> Configure, where you can amened the list.
I suspect you mean the first though.
I'm referring to the TYPE field in the list you referenced earlier. It's there, so why would it be considered a custom field?
I don't see ISSUE TYPE on that list. And, where can I amend the "issue type scheme".
To be sure we're on the same page, here's a partial screenshot of the list I've been perusing...
This is one of the times where language and jargon make things a bit more fuzzy than they should (which is a reason I complain when people use jargon, buzzwords and business-speak, all it does is obscure meaning)
Atlassian are inconsistent in the display of "Issue Type". In this case, "type" does definitely mean "Issue Type". Most of the inconsistency is down to screen space - "issue type" is long, compared with an icon.
So, it is clear we are talking about the "system" issue types now, so we need to look at the issue type scheme for the project. You should just go to the project admin and look for the issue types in use there.
This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs