For this you can use de Save Public functionallity that already exist!

Shelly, have you tried the save public functionality as mentioned? It seems like it'll do as your idea suggests. If it doesn't, please follow up here or elaborate?

Hi, we are aware of the public reports and we do use them, but we have very large user community and do not want the list of public reports to become long and unorganized.  The publicly saved reports should be of interest to all the users, not just a small group.

The users work many times in small groups to review and prioritize the records in the system, requiring they review the same report prior to their meetings:  exporting to another format defeats a main purpose of the app, and having each person manually build the same report is redundant.  

Our application is also growing scope, which sometimes requires changes to the underlying data structure, which can break saved reports.  If we were able to share reports in these groups, one person in that team could rebuild the reports for everyone to access, saving them time.  And, the more sophisticated users could create more impactful reports for the other team members.

We've also considered having one person build and manage the public reports, but that takes away the self-service benefits, and could still result in a large list of public reports.

We also fully support this kind of request!

From our side we would like to have kind of quick share of the report's resultset (which expected to have quite short lifecycle, i.e. minutes or a day-two, i.e. there is no reason to save such configuration anywhere in the system) among colleagues.

It would be great to have some quick, typical use case implemented like:

1. Setup some filters in the reports (like Interactive Grid/Report component's based)
2. Copy/paste URL into the Slack to the team's chat
3. All the interested parties upon clicking the URL will see the report with the same filtering (as user setup for himself on the step #1 above) applied.

Another thing to take into consideration when creating saved reports: a saved report (either Public or the new Shared option) may rely on columns that are hidden for some users because of column Authorization or Server-side condition.

Is this feature going to be adopted soon by Oracle-Apex development or are Oracle happy for customers to consider alternative non-oracle offerings that are quicker to deliver features desired I wonder (nudge nudge).
I cannot count the number of times my user community have wanted this (not full public, but groups of users can share report creation). 
Forgive me if this is resolved, please point me to the solution if it is :)

I just got a question today from an application owner asking if it was possible to do this. She wanted to create the report herself and share it with an executive. This would be a useful feature.

Upvoted.  This feature would be utilised by NSW Health.  Thank you @shelly.simpson for raising this idea.