Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×I've created a filter in Jira for our AirTable specialist to use to import some data into AirTable. The issue we are having is somewhere along the way the filter is being changed from the project name to the project ID so it is not working. The filter is written like this...
project in ("OMS", "Order Management", "Order Sourcing", "Fulfillment") AND issuetype not in (Defect, "PROD Defect") AND createdDate >= startOfYear() ORDER BY key
but its being translated (somewhere along the way to )
project in (10254, 10255, 10256, 10257) AND issuetype not in (Defect, "PROD Defect") AND createdDate >= startOfYear() ORDER BY key
Here's the message we are getting on the airtable side...
A value with '10254' does not exist for the field 'project'
Some of the filters I created worked fine, but several of them are not.
The translation is done to shorten an avoid mistakes. The project names are translated to the project id's
Some the name corresponds to an idea in the system.
There are 2 things that can be wrong.
But the most obvious is, that the users from the airtable side don't have browse access to the project with ID 10254.
Check the project permissions and see which roles, groups or users have browse permissions on the project with ID 10254
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello, Good day. Looks like users have lost "Browse project" permission this could be one of the reason why users see the project ID. Could you please check the browse project permission for these users ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks. Solved the issue because we were using a service account for this work and it was not part of the regular User permissions.
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.