This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
1. Number of users who have run the report - RB 7.0.3 provides the time and name of the person who last executed a report. It does not keep count of unique users who run a report.
2. Total number of times the report has been executed - RB 7.0.3 provides a count of how many times the report has been executed
3. Time of execution - RB 7.0.3 provides the last report run time
4. Over which dashboard/usage it is linked - this is not possible today. It would need a foundational app idea. Pls create a separate idea against the ELM Foundation.
Concerning your questions:
This is actually not enough : we would like to have the complete list of the users who did run the report: to have the possibility to inform them that the report has been changed, will be retired, etc...
This is also an important info to have, so to know in which dashboard, there is a need to modify infos (such as parameters, etc...)
JRS team updated Report Builder, see https://jazz.net/blog/index.php/2023/03/16/report-builder-7-0-3-beta/ for details. Specifically for your suggestion:
1. Number of users who have run the report - RB 7.0.3 beta provides time and name of the person last executed a report. It does not keep count of unique users who run a report. Is this enough?
2. Total number of times the report has been executed - good suggestion. This is not collected today
3. Time of execution - RB 7.0.3 beta provides time of report execution
4. Over which dashboard/usage it is linked - this is not possible today. It would need a foundational app idea. Pls create a separate idea.
5. Potentially store information about whether a particular user "favorites" or likes the report as well - this would be subjective information based on a user preference. It is better to use count under (1) and (2) instead to sort reports by "Popularity", "Usage" or "Frequency".