You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the logs of an application, the API filtering shows options for all APIs that a user has access to, not only the APIs to which the API is subscribed.
To Reproduce :
Steps to reproduce the behaviour:
Create an API on any user and do not subscribe it to any applications
Open the user's Default application and open the application Logs.
In the Filters section, click the API filter. The new API, which is not subscribed to the app, will appear as a filtering option.
This applies to APIs that the user owns and also APIs that belong to a group of which the user is a member, regardless of whether the API is subscribed to the app.
Expected behaviour :
API filtering in the logs of an app should only allow filtering for APIs to which the app is subscribed.
Current behaviour :
Filtering can be done for any API the user has access to in addition to the app's subscribed APIs.
Desktop :
Environment: 3.20.9, 3.19.15
Browser Chrome
* Please see Zendesk Support tab for further comments and attachments.
The text was updated successfully, but these errors were encountered:
Describe the bug :
In the logs of an application, the API filtering shows options for all APIs that a user has access to, not only the APIs to which the API is subscribed.
To Reproduce :
Steps to reproduce the behaviour:
This applies to APIs that the user owns and also APIs that belong to a group of which the user is a member, regardless of whether the API is subscribed to the app.
Expected behaviour :
API filtering in the logs of an app should only allow filtering for APIs to which the app is subscribed.
Current behaviour :
Filtering can be done for any API the user has access to in addition to the app's subscribed APIs.
Desktop :
* Please see Zendesk Support tab for further comments and attachments.
The text was updated successfully, but these errors were encountered: