Like the NeedDataSource, it will be nice if there was a PreRender event or similar.
So that way I could programmatically adjust elements based on the report parameters. Example: a column selection parameter (dropdown) that would then in the 'PreRender' remove or hide the columns from a table if the column name isn't in that multivalue parameter.

When a date is set as a report parameter in the HTML5 viewer, it formats the parameter as a JSON date using a timezone.  Where no time is specified this results in a time part added to the date when received at the server.  This is a problem, especially for browser in a negative offset zone, e.g. US, where upon the date goes to the previous day.  Please add support for parameter types of date, where no time is present and no conversion is done anywhere.

This is not a clone. It's a new request I had to add, since the old was closed with a technically fault answer. By technically fault I mean possible, but in real scenario unusuable.

F.e Jasper's SubReports have a property called DataSource. The sub-reporst uses this dataSOurce for rendering it content. The DataSource is always set on the Main report. Everything via designer, no need for coding. So I'd like to see such a possibility in telerik reports.

The suggested solution - with the bindings http://www.telerik.com/forums/how-to-bind-the-datasource-of-a-subreport-in-the-designer is technically wrong. It assumes that the child report knows at which level he resides inside the main report. The child report (or it's binding) should have not such info embedded. Let's see on an example. Let's have a dataset:
User.Address
User.PostalAddress
User.Wife.Address
User.Wife.PostalAddress

The dataset should be bound to the main report. The main report should have 2 sub-reports (address and postal addres). It can have an another sub-report (for wife data) which then would again have 2 sub-reports inside for addresses.

Using the technically wrong solution, the addresses for the main user should have a binding expr. like: =ReportItem.Parent.DataObject.xy and the wife's addresses have like: =ReportItem.Parent.Parent.DataObject.xy

There is a big problems with such a binding: the child must know the hierarchy of the data.

The technically clean solution is to have a dataset assigned to the main report. When adding a sub-report to the main report, via binding we should set the new data-source for the sub report. something like: MainReport.Data = dataSource. SubReportAddress = dataSourceOfTheCurrentReport.Address. SubReportWife = dataSourceOfTheCurrentReport.Wife and inside "wife report" the next sub-report for address address should have a binding again like: SubReportWifesAddress = dataSourceOfTheCurrentReport.Address

In the Configure Object Data Source Wizard, add a method of filtering the displayed Business Objects.
Where a large number of Business are display, scrolling can be painful to find the required one.

Reporting webapi to support asp.net core

Add a way to force a Page Break in a Multi-Column Report, as opposed to producing a 'Column Break'.
These are 2 separate concepts of a Column Break and a Page Break.

Currently, the designer automatically increase the width of parent containers when a control is moved or resize and goes outside the current parent size.

But this can be problematic with bad paging in some cases. 
As the automatic grow may be needed, I propose to increase the parent size with a settable minimal step:

When having set everything to have a width of 160 mm, just moving some controls can currently increase slightly the size (like 160.23 mm). But if the report has a minimal grow step of say 5 mm, in this case it will be resized to 165 mm, a visible size difference (therefore, layout can be corrected when the grow was unwanted).

The ReportFooter does not print at the bottom of the last page if that page doesn't contain data, even with PrintAtBottom=true set. Can this feature be changes to always print the ReportFooter at the bottom of every page?

just the same like here
https://www.combit.net/en/reporting-tool/pdf-object/

Add a Property for all controls to be able to set whether the control appears on every page of the report. At present the entire Group Header/Footer may be set to appear on every page, but not just a single control.

We required a Barcode and ID. No. to be displayed on every page of the report. It has been really complicated to utilise a series of Group Headers and Sub-Reports to achieve something that should have really easy. The layout of the Report could not be modified as it is set by Government.

Telerik Reporting should facilitate turning the complex into the straight forward.

I find it extremely limiting and frustrating to not have control over how the .NET Report class is initialized, and not being able to pass in any type of object/dependency (either into the constructor or by setting a property.) This makes it very difficult to keep custom reports decoupled from other code modules and make them unit-testable. 

There is the InstanceReportSource, which would have been perfect to solve this problem, but it's apparently deprecated.
http://docs.telerik.com/reporting/t-telerik-reporting-instancereportsource

DevExpress reports for example allow you to create the report instance yourself, and you can pass any objects you want directly into the constructor. 

This is what I find to be the biggest drawback to Telerik reports. 

Currently, adding Sparklines (http://docs.telerik.com/reporting/sparklinesanddatabars#sparklines) or Data bars to the report requires manual formatting of the Graph item (hiding the Axes, Labels etc.).

Let us know if you think the built-in support for this type of chart would be useful when creating reports. Please share your ideas/thoughts in the comments and give a vote for this feature to support it.

An example of Sparklines/Data Bars is provided in our online demos - http://demos.telerik.com/reporting/product-sales?&skinName=silver(Product Sales report).

Thank you.

Please support OData services as built-in report datasource.

We would like to use Telerik Reporting and Report Server but the missing support for OData is holding us back.

Let us know if collapsing report sections in report designer would make the designing of reports more convenient for you.

When reports have more complex structure with a lot of sections collapsing some of them might improve the overall design time experience.

As a reports user I would like more options for Line Styles in Chart plots.
Currently the options are Solid, Dashed and Dotted.
As a start it would be great to replicate the options in the Kendo UI Line Charts dashStyle enumeration:
https://docs.telerik.com/kendo-ui/controls/charts/chart-types/line-charts#configuration-Types

As the perfect option list for me:
Solid
ShortDash
ShortDot
ShortDashDot
ShortDashDotDot
Dot
Dash
LongDash
DashDot
LongDashDot
LongDashDotDot

Thanks

Currently the images loaded in PictureBox item and Style's BackgroundImage property are rendered preserving the item's physical size. This causes scaling when the machine's DPI is different than the image DPI and affects the image quality.
A specific option should allow the images to be rendered without being altered, including applying antialiasing on the target graphics object.

The Labels to be displayed on a Numerical Scale Axis are currently set automatically.
The user can control the scale range via Axis Scale Minimum and Maximum properties. The user can control also the Label Step.
However, the exact Axis Labels to be shown are calculated automatically and cannot be controlled directly by the user.
For example the user cannot force the Axis Labels to start from the Minimum value.

For some reason the export is suppressing leading spaces spaces in front of cells with text so they are not indenting properly. Padding is also ignored.

Please provide an option to launch a sub report directly from within the main report designer (standalone version).
Example, in Crystal reports, if there is a sub report within a report, a user can double click that sub report and it opens it as a new report tab. This is very convenient rather then having to chase down the path to the subreport and open it manually.