Hi all,
If your app defines issue fields note that Atlassian’s recent “optimization” of custom fields may have broken searches for your app as it did for ours.
We are guessing that this community announcement to “optimize” project field schemas was the cause. Announcing project/fields association improvements for company-managed projects - Announcements - The Atlassian Developer Community
Up until a few weeks ago (and for the last 5 years), a newly installed customer could run a jira search/filter like this:
project='DEMO' and ‘Signature Count’ > 0
Now customers receive this error message instead of results:
Field ‘Signature Count’ does not exist or you do not have permission to view it.
The only workaround we’ve found so far is to require customers to add the Signature Count field to the project(s).
We did raise ECOHELP-76025 early this week with the breaking change but so far no response except a downgrade in criticality.
Background:
Our app uses a number of read-only extracted fields to facilitate user searches in filters and dashboards. The “Signature Count” field is declared statically in the app manifest as read-only. The value is extracted from an issue property.
If your app has statically declared fields like the following, recommend testing to see if this optimization also broke searching for you.
"jiraIssueFields": [
{
"key": "signees-field",
"name": { "value": "Signature Count" },
"description": { "value": "eSign: Number of signatures on this issue" },
"type": "read_only",
"property": {
"path": "signees",
"key": "esign.digitalrose.dev",
"type": "number"
}
Regards,
Chris
Digital Rose