Hi,
We are using Jira 7.4.3
I try to understand the usage of the issue.property stuff in JQL and REST.
First question, is there any doc around ?
In JQL, I am able to run
issue.property[development].commits.> 0
It returns a lot of issues. I understand all these issues have a property with key=development ?
I then run a REST call on one of these issues (in the example XVIEW-260) :
curl -u xxxx:yyyyyyy -o IssueProperties.json "https://jira.evs.tv/rest/api/2/issue/XVIEW-260/properties?noSAML"
but get {"keys":[]}, indicating that this issue does not have any property ???
Are these other properties ? Do I do something wrong ?
Very confusing :-(
The latest version of Jira 7.13, does document this kind of JQL field reference over in https://confluence.atlassian.com/jirasoftwareserver/advanced-searching-fields-reference-939938743.html#Advancedsearching-fieldsreference-development[commits].all
However when looking at the Jira 7.4 version of that same document: https://confluence.atlassian.com/jirasoftwareserver074/advanced-searching-fields-reference-921472945.html
You will notice that this document does not include these function yet. These development searching feature in Jira's JQL wasn't technically released to Jira Server until the 7.9 release, see the Jira Software 7.9 release notes for more details. Back in your specific version, this was largely an undocumented JQL search feature. I think this was because it might not have been fully built yet, certainly it wasn't officially released yet.
However there is also a difference here between these development properties and Jira issue properties. The development properties are specific to linked bitbucket/fisheye/github code repos that reference this specific issue. But Issue properties in general don't necessarily rely on another repo tool to utilize them. These properties are better described in the Development documentation https://developer.atlassian.com/server/jira/platform/entity-properties/
These entities properties provide plugins the ability to add/edit their own keys in regards to issue and projects in Jira. These are not always intended to be used by end users in the UI, but they aren't prevented from using them either.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.