I have a requirement to define expressions using JQL.
I would like to reference a field called "Epic Link". However, this field name has a space in it which is causing confusion when processing the command.
The obvious expression to use would be something like 'Epic Link = "xxxx"'. However this returns an error which states "Expecting operator but got ‘Link’" which suggests that the space in the field name has been interpreted to mark the end of the field name.
So, what should I my expression look like?
I have tried the obvious things; putting the field name in quotes or brackets, substituting the space with characters like underscore, removing the space, but not had any luck.
The only online help I've found on this so far is at https://confluence.atlassian.com/jiracoreserver073/advanced-searching-861257209.html#Advancedsearching-epic_linkEpiclink but this just lists the field names (including spaces) and tells me how to handle the contents of text fields but not the field names themselves.
Any help would be much appreciated!
(Note, My requirement is to filter data being pulled from Jira into another application - the JQL expressions are to be written in the other application so it is possible the application I'm using is not processing the expressions correctly. I have contacted the support team for the other application as well to check this.)
Thanks very much for your quick response!
yes, that's the kind of advice I'm looking for. Though I have tried several things like this to no avail, e.g.:
"Epic Link" = "xxxx"
[Epic Link] = "xxxx"
Epic_Link = "xxxx"
You suggest that the first of these should work? At the moment it doesn't work for me. I shall keep poking. As I said though, I'm writing this JQL query in another application, so it's possible that application is at fault.
I'm using Aha!
I have also been notified by our IT Dept that we've been having some 'network issues'. This may explain why my email client keeps saying "Trying to connect..." and may also be the cause of my problem between Aha! and Jira.
I have re-tried the process using your advice above and it has just worked!
Thanks very much for your help
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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