You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "sainikhilsamineni (via GitHub)" <gi...@apache.org> on 2025/07/03 06:42:22 UTC
[D] time range filter [superset]
GitHub user sainikhilsamineni created a discussion: time range filter
@dosu in superset dashboards why am i getting access denied for only the filter of time range type when i am able change others?
GitHub link: https://github.com/apache/superset/discussions/34046
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] time range filter [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: time range filter
<!-- Answer -->
This isn't expected—read-only users should be able to interact with and apply time range filters just like other filter types, as long as they have dashboard access. There are no special restrictions or recent changes in Superset that would block only time range filters for users with dashboard read permission; all native filters use the same backend and frontend logic for value application, and permissions are enforced at the dashboard level, not per filter type ([source](https://github.com/apache/superset/issues/33599)).
If you see "access denied" only for the time range filter, it's likely due to a bug, a frontend/backend state mismatch, or a misconfiguration—possibly a context or session issue, or a problem with how the filter is set up. Try these steps to isolate the problem: use a different browser or incognito mode, check if the issue happens for other dashboards or users, and look at your browser's network tab for failed requests and error details when you try to apply the time filter. If you can, share the exact error message or a screenshot, and confirm your Superset version—this will help pinpoint the root cause.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=0067690b-176d-478c-ab6c-fc4230882340) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/34046#discussioncomment-13648906
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] time range filter [superset]
Posted by "sainikhilsamineni (via GitHub)" <gi...@apache.org>.
GitHub user sainikhilsamineni added a comment to the discussion: time range filter
@dosu not editing filters, just passing values by selecting range type then configuring time range eg. last, current, custom etcc.
GitHub link: https://github.com/apache/superset/discussions/34046#discussioncomment-13648667
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] time range filter [superset]
Posted by "sainikhilsamineni (via GitHub)" <gi...@apache.org>.
GitHub user sainikhilsamineni added a comment to the discussion: time range filter
@dosu my database is a time-series db missing time-column is not a problem. My user has only dashboard read permission and is able to change values for other filters and apply. But not able to change date/time values in the time range filter.
GitHub link: https://github.com/apache/superset/discussions/34046#discussioncomment-13648884
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] time range filter [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: time range filter
<!-- Answer -->
Thanks for clarifying! Based on the code and docs, there isn’t a special permission for using time range filters—if you can use other filters, you should be able to use time range as well. The “access denied” error for just the time range filter usually points to a mismatch in dashboard access, a session/cache issue, or a bug in how the filter state is handled—not a dataset or filter-specific permission. Missing a temporal column would just make the filter unavailable, not trigger an access denied error.
Could you confirm:
- Does your dataset have at least one visible date/time column?
- What is the exact error message or UI you see (screenshot helps)?
- What Superset version are you on?
Also, try clearing your browser cache or using a different browser to rule out session issues. If everything looks correct and you still get the error, it could be a context mismatch or a bug in the filter logic. Let me know the details above and I can help you dig deeper!
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/d1a02a00-bee7-46dc-b564-e6ab782a68e4?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/d1a02a00-bee7-46dc-b564-e6ab782a68e4?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/d1a02a00-bee7-46dc-b564-e6ab782a68e4?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/d1a02a00-bee7-46dc-b564-e6ab782a68e4?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/d1a02a00-bee7-46dc-b564-e6ab782a68e4?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/d1a02a00-bee7-46dc-b564-e6ab782a68e4?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/d1a02a00-bee7-46dc-b564-e6ab782a68e4?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/34046)
GitHub link: https://github.com/apache/superset/discussions/34046#discussioncomment-13648725
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] time range filter [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: time range filter
<!-- Answer -->
There isn’t a separate permission for time range filters in Superset—permissions for all native filters are tied to dashboard edit rights. If you can edit other filters but get “access denied” only for the time range filter, the most likely cause is that the dataset used by the time filter doesn’t have any temporal (date/time) columns. In this case, the frontend disables or blocks the time range filter, but this is a dataset configuration issue, not a permissions one.
Check that your dataset(s) have at least one temporal column configured. There are no known bugs or recent changes that would cause access denied errors specifically for time range filters if you have edit rights to the dashboard. More details on this permissions model can be found [here](https://github.com/apache/superset/issues/33599) and on dataset requirements for time filters [here](https://github.com/apache/superset-frontend/src/dashboard/components/nativeFilters/FiltersConfigModal/FiltersConfigForm/FiltersConfigForm.tsx).
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/b02a4b89-10fb-451c-a58e-3d41016d920d?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/b02a4b89-10fb-451c-a58e-3d41016d920d?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/b02a4b89-10fb-451c-a58e-3d41016d920d?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/b02a4b89-10fb-451c-a58e-3d41016d920d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b02a4b89-10fb-451c-a58e-3d41016d920d?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/b02a4b89-10fb-451c-a58e-3d41016d920d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b02a4b89-10fb-451c-a58e-3d41016d920d?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/34046)
GitHub link: https://github.com/apache/superset/discussions/34046#discussioncomment-13648450
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] time range filter [superset]
Posted by "sainikhilsamineni (via GitHub)" <gi...@apache.org>.
GitHub user sainikhilsamineni edited a comment on the discussion: time range filter
@dosu my database is a time-series db missing time-column is not a problem. My user has only dashboard read permission and is able to change values for other filters and apply. But not able to change date/time values in the time range filter.
GitHub link: https://github.com/apache/superset/discussions/34046#discussioncomment-13648884
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] time range filter [superset]
Posted by "sainikhilsamineni (via GitHub)" <gi...@apache.org>.
GitHub user sainikhilsamineni edited a comment on the discussion: time range filter
@dous I found the issue. There is permission "can time range on api" that has to enabled for passing the time range values. Closin this disussion
GitHub link: https://github.com/apache/superset/discussions/34046#discussioncomment-13648937
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] time range filter [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: time range filter
<!-- Answer -->
Thanks for clarifying! Based on the code and docs, there isn’t a special permission for using time range filters—if you can use other filters, you should be able to use time range as well. The “access denied” error for just the time range filter usually points to a mismatch in dashboard access, a session/cache issue, or a bug in how the filter state is handled—not a dataset or filter-specific permission. Missing a temporal column would just make the filter unavailable, not trigger an access denied error.
Could you confirm:
- Does your dataset have at least one visible date/time column?
- What is the exact error message or UI you see (screenshot helps)?
- What Superset version are you on?
Also, try clearing your browser cache or using a different browser to rule out session issues. If everything looks correct and you still get the error, it could be a context mismatch or a bug in the filter logic. Let me know the details above and I can help you dig deeper!
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=d1a02a00-bee7-46dc-b564-e6ab782a68e4) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/34046#discussioncomment-13648725
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] time range filter [superset]
Posted by "sainikhilsamineni (via GitHub)" <gi...@apache.org>.
GitHub user sainikhilsamineni closed a discussion: time range filter
@dosu in superset dashboards why am i getting access denied for only the filter of time range type when i am able change others?
GitHub link: https://github.com/apache/superset/discussions/34046
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] time range filter [superset]
Posted by "sainikhilsamineni (via GitHub)" <gi...@apache.org>.
GitHub user sainikhilsamineni added a comment to the discussion: time range filter
@dous refer the updated comment with a screenshot, superset version 5.0.0
GitHub link: https://github.com/apache/superset/discussions/34046#discussioncomment-13648937
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] time range filter [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: time range filter
<!-- Answer -->
This isn't expected—read-only users should be able to interact with and apply time range filters just like other filter types, as long as they have dashboard access. There are no special restrictions or recent changes in Superset that would block only time range filters for users with dashboard read permission; all native filters use the same backend and frontend logic for value application, and permissions are enforced at the dashboard level, not per filter type ([source](https://github.com/apache/superset/issues/33599)).
If you see "access denied" only for the time range filter, it's likely due to a bug, a frontend/backend state mismatch, or a misconfiguration—possibly a context or session issue, or a problem with how the filter is set up. Try these steps to isolate the problem: use a different browser or incognito mode, check if the issue happens for other dashboards or users, and look at your browser's network tab for failed requests and error details when you try to apply the time filter. If you can, share the exact error message or a screenshot, and confirm your Superset version—this will help pinpoint the root cause.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/0067690b-176d-478c-ab6c-fc4230882340?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/0067690b-176d-478c-ab6c-fc4230882340?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/0067690b-176d-478c-ab6c-fc4230882340?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/0067690b-176d-478c-ab6c-fc4230882340?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0067690b-176d-478c-ab6c-fc4230882340?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/0067690b-176d-478c-ab6c-fc4230882340?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/0067690b-176d-478c-ab6c-fc4230882340?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/34046)
GitHub link: https://github.com/apache/superset/discussions/34046#discussioncomment-13648906
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] time range filter [superset]
Posted by "sainikhilsamineni (via GitHub)" <gi...@apache.org>.
GitHub user sainikhilsamineni edited a comment on the discussion: time range filter
@dosu not editing filters, just passing values by selecting range type then configuring time range eg. last, current, custom etcc. For other filters the values are getting fetched from a tables column
GitHub link: https://github.com/apache/superset/discussions/34046#discussioncomment-13648667
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] time range filter [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: time range filter
<!-- Answer -->
There isn’t a separate permission for time range filters in Superset—permissions for all native filters are tied to dashboard edit rights. If you can edit other filters but get “access denied” only for the time range filter, the most likely cause is that the dataset used by the time filter doesn’t have any temporal (date/time) columns. In this case, the frontend disables or blocks the time range filter, but this is a dataset configuration issue, not a permissions one.
Check that your dataset(s) have at least one temporal column configured. There are no known bugs or recent changes that would cause access denied errors specifically for time range filters if you have edit rights to the dashboard. More details on this permissions model can be found [here](https://github.com/apache/superset/issues/33599) and on dataset requirements for time filters [here](https://github.com/apache/superset-frontend/src/dashboard/components/nativeFilters/FiltersConfigModal/FiltersConfigForm/FiltersConfigForm.tsx).
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=b02a4b89-10fb-451c-a58e-3d41016d920d) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/34046#discussioncomment-13648450
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org