HELP ME! I want to use JQL in command line

[Hao Bui]

I am using Export function of QMetry for Jira for get Test Case information. I export data by command line. I want to filter the test case result only contain TestCase. I try use JQL clause but the error is appear. I not sure about syntax correct. Could you help me about syntax?

[Reshma Padkil]

Hi @Hao Bui ,

Please get in touch with  QMetry Support with exact JQL that you are using. We will be happy to help you.

[brbojorque]

Hi @Hao Bui , can you provide the exact JQL you are trying to execute?

[Hao Bui]

I run the command line as below, please take a look:

java -cp ImportExport-1.7.5.jar com.infostretch.importExportUtility.cliController.Main user@example.com   --my email

<removed> -- my token

<removed> --my api key

https://example.atlassian.net --my host

C:\Export\QTM_2019-06-20_Export.xlsx --my path 

issuetype IN ("TestCase") -- my JQL

PHW --my project key

Best.

Hao.

[Reshma Padkil]

@Hao Bui ,

Yes, the JQL is wrong. It should be - issuetype in ("Test Case").

"Test Case" issue type has space.

[bryan bojorque]

Hi @Hao Bui , first of all you posted all of your credential in public. Please regenerate your API key and Token so no one can exploit it.

I don't see nothing wrong with the JQL.

My question is your issuetype "Test Case" or "TestCase" either way if both do not exists it would have resulted to issuetype does not exists.

Maybe fix the error reporting to the actual error being displayed in the search page.

It seems to be that there is an escaping issue here, the error is a bit weird to me.

[Earl McCutcheon]

Hi @Hao Bui ,

I removed the Token and sensitive content from your post above as this information is publicly visible in this forum and has been exposed for the last 9 hours and anyone with the information can access and modify your data from the API impersonating your account.

I would recomend going to https://id.atlassian.com/manage/api-tokens and revoking the original API token, and creating a new one, to avoide any unwanted users from accessing the data.

Regards,
Earl

[Hao Bui]

Thanks all, It is only fake Token and API Key

[Earl McCutcheon]

Hey  @Hao Bui ,

Good to hear and thanks for the confirmation on that part whenever we see something that looks like it could be a security leak we try to jump on it asap.

Regards,
Earl