Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-49180

Error Message for Filter that doesn't Exist or is Private

    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      Summary

      The error message for invalid or missing filter too vague.

      Current error message

      Unable to load events of Project Launches (b24brb32d-6a6e-42f1-kf7d-138881147207): Its search filter is not valid.

      Improvement Request

      Have a more descriptive error message indicating missing or private filter.

            [CONFSERVER-49180] Error Message for Filter that doesn't Exist or is Private

            Atlassian update

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.

            For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.

            Thanks again.
            Regards,
            Confluence Product Management

            Adam Barnes (Inactive) added a comment - Atlassian update Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence . Thanks again. Regards, Confluence Product Management

            Understood. The original ticket was about a slightly different issue, but regardless we will add this to the backlog. Now that we've moved calendars to spaces we should simply hide calendars that users do not have access to (i.e. similar to how page restrictions work; if you don't have access to a page it simply doesn't appear in the page tree of the sidebar).

            snorrish (Inactive) added a comment - Understood. The original ticket was about a slightly different issue, but regardless we will add this to the backlog. Now that we've moved calendars to spaces we should simply hide calendars that users do not have access to (i.e. similar to how page restrictions work; if you don't have access to a page it simply doesn't appear in the page tree of the sidebar).

            snorrish Ok, I'll try to explain more, although I think that what I wrote previously should be explanatory enough.

            1. Person A creates 10 team calendars in space and restricts 8 of them to smaller group of users (let's say to Leads group) - pretty common operation I think, that's why Restrictions are there
            2. Person B, who is not in Leads group, clicks the Calendars button in the left menu and gets 8 errors. Every single time.

            It would help (at least as a quick fix) to put those messages BELOW the calendars so users don't need to scroll down to see calendar every time.

            Nikola Bornová added a comment - snorrish Ok, I'll try to explain more, although I think that what I wrote previously should be explanatory enough. Person A creates 10 team calendars in space and restricts 8 of them to smaller group of users (let's say to Leads group) - pretty common operation I think, that's why Restrictions are there Person B, who is not in Leads group, clicks the Calendars button in the left menu and gets 8 errors. Every single time. It would help (at least as a quick fix) to put those messages BELOW the calendars so users don't need to scroll down to see calendar every time.

            There isn't currently a way to dismiss the TC errors. I imagine you must have embedded private calendars on a page? Can you explain why you would do this (why would you want the view permissions for the page to be different than the view permissions for the calendars embedded on it)?

            snorrish (Inactive) added a comment - There isn't currently a way to dismiss the TC errors. I imagine you must have embedded private calendars on a page? Can you explain why you would do this (why would you want the view permissions for the page to be different than the view permissions for the calendars embedded on it)?

            One more thing for this - is there any way how to remove the errors and warnings in the Calendars page? We have lots of private calendars connected to projects and when you open Calendars in some project, you have first huge list of errors and warnings about everything you can't see which makes it not very practical and usable (you must scroll down through all the errors and warning each time)

            Nikola Bornová added a comment - One more thing for this - is there any way how to remove the errors and warnings in the Calendars page? We have lots of private calendars connected to projects and when you open Calendars in some project, you have first huge list of errors and warnings about everything you can't see which makes it not very practical and usable (you must scroll down through all the errors and warning each time)

              Unassigned Unassigned
              namir Nursihah Amir (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: