Let us know how we can make Jedox even better!
The comment pane is barely useful... Because it allow comment but on nothing, I think the main purpose is about leave a comment on the whole application. But no one use it daily.
The comment pane could be useful in a test phase for example, indeed, the tester could leave a comment in each report he consulted and then the develloper could check the comment on each report to correct the error found by the tester.
It's a use case but with a system a little it more complex this should really useful.
In other case you should delete this feature if you don't want to evolve it or set it at FALSE by DEFAULT in Administration > Settings
Thank you for your great idea. While we cannot commit to a specific target version, we will consider adding it to our future internal backlog. If you can add further information about the context of this feature, please add it here so we can evaluate it more fully.
Here's the detailled idea :
On the grey ribbon(the one with the "Recalculate" button, the "copy/paste/cut" button, and the other button...) corresponding to the report you can put another button called "View comments". This button will be a simple button on simple report, but when we open a frameset it become a drop-down list(when we click on it) with all reports contains in the frameset. Once we click on it the comment panel show-up(before this the comment panel is completly hidden because this panel is very annoying and space-consumming), and it show the list of the comment link to the report. Each comment have at least those attributes :
datecreation, datemodification, by(the user who write the comment)
We could access to this comment section by right clickling on any report to show-up the comment section linked to the clicked report.
In the background those comments should be store in a cube to be manage in the future. In my first example I was talking about "test phase" in a project, I think it should be great to have one more attribute(it should be great if this attribute was activable or not) : a binary attribute (1 or 0) that should correspond for example to a task that is done or not done yet. With this attribute we could, after the first "test phase" on a project delete all "done" comment by ETL because those comments are store in a cube.