JQL to find related projectype

[Anand Patel]

Hi

i am getting this error when i am doing REST call as "https://.../rest/api/2/search?jql=projectTypeKey = INTEGRATION and issueType = BUG and Description !~ REST "

Error : Field 'projectTypeKey' does not exist or you do not have permission to view it.

and similarly

when REST call is "https://.../rest/api/2/search?jql=customfield_10023 = 0001041 and issueType = BUG and Description !~ REST "

Error : Field ''customfield_10023" does not exist or you do not have permission to view it.

it allows issueType and description to be called.. but givving problem for projectTypeKey ,customfield_10023.

Can somebody tell me what changes i need to do in REST call.??

[Warren]

Hi Anand

projectTypeKey is obviously wrong, it should just be project, but the project name needs to be in quotes, so

?jql=project="INTEGRATION" and

Rather than customfield_xxxx, you need to use the actual name of the custom field.

As a test, whatever you have in the jql=... section should successfully run as a standard JQL filter within Jira - I often write the JQL within Jira first, then apply it in my code.

Hope this helps

[Anand Patel]

Hi Warren, 

Thank for reply

yes i tried in JIRA also there also it is giving same error..

Project="IN" works fine in JQL but 

projectTypeKey="SOFTWARE" 

so i was wondering there must be some way to write it in JIRA.

Actually i got projectTypeKey in response of REST call.. so i was just trying to use this field to filter issue JQL and i tried custom field name still it is giving same error.??

[Warren]

Hi Anand

If you're in a filter within Jira, after project= if you start typing the name of the project, it should offer matches e.g. my project is Digital Development and after typing dig it already offers me the full name. You can also use the key e.g. ours is DDT so I can type project=ddt and it will also offer me the full name. IN is the same as =, except that it allows you to specify more than one project (which you're not doing).

If you're not having the same behaviour, possibly it's a permissions thing. You will need at least read permissions on the project to be able to do it.

You need to get this working in Jira before you try the API, so keep trying project and not projectTypeKey

[Warren]

In fact, in Jira, just typing project= and then the spacebar, should show you all the projects that you have access to