As a user, there should be an error on the UI when entering an invalid SPACE or SCOPE values on a reporter

Steps to reproduce:

  1. Create a report block that contains a content reporter
  2. on the Space field OR on the Scope field, enter @seld (any invalid value that starts with @)
  3. Add a report-info > content:title
  4. Save the page

The page will show the entire page title for that space.  The logs will show the following error:

2018-10-11 10:28:33,107 WARN [http-nio-8090-exec-12] [support.core.impl.DefaultParameterAssistant] invoke Exception while processing an interceptor: '@seld' is not a recognized space category
 -- url: /display/OIPBP/SRSUP-2604 | page: 9994242 | traceId: 42cbbc0debe2aa0c | userName: confadmin | referer: http://localhost:8090/pages/editpage.action?pageId=9994242 | action: viewpage '@seld' is not a recognized space category

Note that the page looks like it's working as expected since it's producing a result, but the result is inaccurate.  There should be the same ERROR/Warning on the UI, not just the logs. 

  • Immanuel Siagian
  • Oct 11 2018
  • Needs review
  • Attach files
  • Guest commented
    11 Nov, 2022 01:36pm

    From your support engineer

    We can confirm that when the Spaces field is filled incorrectly, then that field will be ignored and instead Content Reporter will start to query everything (including pages, attachments and more) from Confluence and the instance can easily go down when there is enough data to consume the heap.

    So as you seem to know a mistake can be made and bogus value entered inside field Space, which can make Confluence go down, I am still wondering why this isn't considered critical and fixed already!