The following JQL doesn't return any results, but I know for sure that there are issues that should be returned.
project = "XXX" and issue.property[development].commits > 0
Is there any setting you need to enable in JIRA in order to query on issue.property[] values? I'm running JIRA 6.2.1 and Stash 3.10.0.
Thanks!
That format of JQL is only supported in JIRA 6.4 and above. It is not a publicised feature due to the fact it has a number of caveats that impact its usability.
The information in JQL is only optimistically updated assuming you have JIRA and Stash connected via Applinks correctly (see https://confluence.atlassian.com/display/STASH/Linking+Stash+with+JIRA and https://confluence.atlassian.com/display/JIRA/Integrating+JIRA+with+Stash).
In certain cases, changes in Stash will not be updated in JIRA unless you manually view the issue or view it as part of release hub https://confluence.atlassian.com/display/JIRA/Checking+the+progress+of+a+version.
These cases are:
Hope this helps explain things
It is doc'd though, if not well publicised: https://developer.atlassian.com/jiradev/jira-architecture/building-jira-add-ons/jira-entity-properties-overview . That page implies that is available from 6.2.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you try using the rest api to verify that an issue has at least that property? https://developer.atlassian.com/jiradev/jira-architecture/building-jira-add-ons/jira-entity-properties-overview#JIRAEntityPropertiesOverview-Example2:Retrievingdata
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I get back an empty dictionary if I make the request they list as an example. Though, I thought Stash was populating these properties? $ curl -u user:pass -X GET http://jira.myinstance.com:8080/rest/api/2/issue/ISS-33/properties/ {"keys":[]}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well, but, at least you know which end has the problem now. Have you tried support?
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.