The print functionality cannot be used in Google Chrome 77.0.3865.75 (lastest update).  The following error is displayed in the console of the browser: Resource interpreted as Document but transferred with MIME type application/pdf.

As an alternative, you can use other web browsers for printing. 

For our Customers a major drawback to creating form type reports (Invoices, Purchase Orders etc.) using Telerik Reporting is the inability to show vertical dividing lines between data columns in the 'Detail' section of the report that extend all the way down the page to the Page/Report footer. We were able to do this with Crystal Reports. But we plan to migrate all our Crystal reports to Telerik.

It would be nice, if not required by our client, to have 100% Web-based, Rich, Ad-hoc Reporting Solution.
Something similar to the one in ComponentOne Active Report 

Please add to the Telerik reporting step line chart the same functionality that exists in the kendo ui step line chart.   There is an attribute for justified = true that allows the line to step directly to the marker rather than having them placed in the middle of the step.  Please see the attached images for the current result vs the desired result.

To have a better performance would be nice to cancel report rendering automatically or manually. 
If I am asking for a big report and after I change parameters and request new report, the previous request is still in progress and it is not going to be cancelled. Therefore I see high memory consumption on continuously refreshing a reports with a big data and after some time I see complete slow down of the Reporting Service and of course slow down of the server itself. The memory in this case is not released and Reporting Service crashes sometimes.

I have scenario like this: Sam requests a product report from company A.  Marvin creates the report and send it back to Sam.  Sam imports it.  It would be best if Marvin (Author of the report) could specify all the meta data so that Sam doesn't have to enter these things.

In my case I need following metadata for the report:

• Keyword: some external tags...
• Description: a description so that the user can understand what this report will show and the purpose of the report.

We often receive feedback regarding hard/impossible editing of reports after they are exported to Word format.
The existing rendering mechanism will produce Word tables which are harder for manual editing - http://docs.telerik.com/reporting/designing-reports-considerations-word

Let us know in comments about your experience with editing reports exported to Word format so we can understand more clearly what is required from Reporting Word rendering extention.

I used https://docs.telerik.com/reporting/html5-report-viewer-howto-use-it-with-reportserver to setup an HTML5 Report Viewer with Report Server. After running the project, the viewer does not load. It seems that it could not find telerikReportViewer script. 

Workaround: Instead of

<script src="/api/reports/resources/js/telerikReportViewer"></script>

use absolute path:<script src="http://yourreportserverhost:83/api/reports/resources/js/telerikReportViewer"></script>

Add the ability to control the distance between the Image and the Text for a Check Box & Radio Box. A space may be used but this does not work where the text wraps to another line and does not give the required level of control.

The Telerik Reporting only support fixed size page now.
But sometimes we need continues-roll paper mode.(like: receipt paper)

Some reporter tools: ActiveReports, it has 3 mode:(Page Reports,  RDL Reports,  Section Reports)

On "Telerik Forums / Reporting Forum" there is already some people asked it before 2 years ago. But until now the basic feature not release....

It would be good if the table headers can be frozen.  This can  be really useful in case of a big report which is displayed on a single page.

It would be very handy, if the value property of the PictureBox would resolve images from base64 strings besides the Image, Image byte[], relative or absolute URI.
It should be fairly simple to implement. I wrote my own user function for this. It would be beneficial to have this out of the box.

[Function(Category = "Image", Namespace = "ImageFunctions", Description = "Converts a base64 string to an image byte array")]
public static byte[] ConvertFromBase64(string imageString)
{
    if (imageString != null)
    {
        // Convert base 64 string to byte[]
        byte[] imageBytes = Convert.FromBase64String(imageString);
        return imageBytes;
    }
    else
    {
        return null;
    }
}