Difference between type and issuetype in JQL Edited

[Jack Nolddor _Sweet Bananas_]

Someone can tell me the difference if any between type and issuetype field on JQL?
I have same question with key and issuekey fields..., are they different in any way?

[Nic Brough _Adaptavist_ · Accepted solution]

It's not well-documented, but there are a handful of "aliases" in Jira.  Key is an alias for issuekey, and type is an alias for issuetype.  You've spotted the two main ones!

The aliases can be clobbered - you can create custom fields with the same name which then become the first place Jira looks when you type in the alias, but I'd try to avoid doing that in every case, as it just confuses your humans.

[Cristian Rosas _Tecnofor_]

"Your humans"

❤

[Alexey Matveev _cPrime_]

Hello,

There is not difference.

[Matt Doar__ LinkedIn]

I use "issue type" when I want to avoid confusion. Just like I say "Jira project" instead of "your company project".

To see all the aliases that exist go to /rest/api/2/field as an admin, and look at the clauseNames for each field.

I found the following aliases

[u'issuetype', u'type']
[u'remainingEstimate', u'timeestimate']
[u'updated', u'updatedDate']
[u'originalEstimate', u'timeoriginalestimate']
[u'id', u'issue', u'issuekey', u'key']
[u'created', u'createdDate']
[u'due', u'duedate']
[u'resolutiondate', u'resolved']