GraphQL Filters and Rate Limiting

GraphQL Filters We added extensive filtering options to our GraphQL API to make it easier to find specific entities without wading through all of an organization's data. Filtering is available wherever results are paginated. It lets you filter based on entity properties, use and/or logical operators, and filter based on an entity's relations. Here are some examples of the more complicated queries that you can accomplish using the new filtering: Find all issues with the label bug or defect with a high priority in the workspace assigned to you Find all projects where a particular person is the lead that has open issues and is due in the next month Find all labels that contain the word design, have a high priority, and are associated with issues in a particular team's projects. With our recent changes that let OAuth applications consume webhooks, filtering should make it easier to create real-time API applications that don't need to poll all of the organization's data very frequently. Read more on filtering in our developer's guide. Rate Limiting With the recent changes that help you get the exact data you need from our API (GraphQL filters) and improvements to how you can get real-time updates from us (webhooks), we're starting to roll out rate limiting on our GraphQL API. We're starting without enforcing the limits, but exposing them to you in our API response headers. If you're using API keys to query us or if you're an OAuth app developer, you should look into whether your current usage would get limited after a certain amount of requests. In the next few days we'll also begin sending out emails to API key owners and OAuth app developers who are repeatedly getting limited and asking them to adjust their usage. These changes are necessary to ensure equitable availability of our API for everyone and to prevent potential abuse. If you have any comments or suggestions, please reach out to us on any of the standard channels, such as email, the Slack community (#api channel), or Twitter. Read more on rate limits in our developer's guide. Fixes and improvements Fixed a bug where clicking a PR in issue lists would open the incorrect PR Front and Zendesk are now updated with a more clear message when the linked issue is merged into another and cancelled Highlight the issue comment when opening from a link Fixed some issues in sync where stale data relationships could cause client errors Webhooks now include `organizationId` to differentiate between workspaces when installed using OAuth applications Increased maximum project name length to 80 characters The app now works correctly in Firefox with `resistFingerprinting` enabled Added a warning to issue compose in situations where there are unsaved changes and user reloads the page