Hy,
Where can I find the list of all the standard fields with a description and a format ?
Thank you
Maybe this will help:
https://confluence.atlassian.com/jirasoftwareserver071/advanced-searching-800707146.html
scroll down to :
Reference
In the table, you'll see
>Show list of fields
Open it and there are the standard fields useable by JQL.
Neal
Is there any documentation that shows the definitions of each field (not custom fields, but "out of the box" Jira fields) along with an explanation of how they are to be used?
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.
What do you mean by "standard fields"? The system ones that are built into JIRA and Software?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I mean the field like resolution date or created date for example.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you mean the ones that are built in then?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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 must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nic,
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...
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
And to further clarify, here's the analogous field in Atlassian's own JIRA for Confluence Server.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
OK. Turns out my people added a field for Bug/Suggestion/etc. and it is called Type.
And agreed on the confusion with the terminology/inconsistency.
No further help needed. Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does Jira Cloud have the same list of Standard fields as Jira Server?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not quite, but it depends on whether you're on Classic or Next-gen projects.
More important though, where they do differ, it's only on fields that humans don't get to enter directly, so it won't really affect your usage.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Show up and give back by attending an Atlassian Community Event: we’ll donate $10 for every event attendee in March!
Join an Atlassian Community Event!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.