The width of a resource does not always match the column(s) underneath it, resulting in the resources shifting to the left in relation to the column(s) below. It appears to be about 1 pixel  difference per resource which becomes more noticeable with multiple resources .If you resize the form the resources will come close to matching the column(s) before jumping back to the full difference again. This issue can be demonstrated in the Scheduler->Grouping demo

Currently, a time range of working ours is valid for all days in the week. There could be a rule that sets a specific range for some days of the week, leaving another range of hours for the rest of the days.

ADD. Scheduler - add possibility to increase the height of the line showing the current time

Steps to reproduce:
1. Add a RadSchduler to a form (No need to add appointments) 
2. Set the active view type to Timeline 
3. Set the Appointmentheight property of the timeline view element to 50 
4. Run the project, right-click on the scheduler and select Next View You will see a NullReferenceException exception.

The issue is when you drag up or drag down the top or bottom of the appointment i.e extend or decrease the slot.
The error I get with that same codebase is
Object reference not set to an instance of an object.
inner exception null

Source: Telerik.WinControls.Scheduler

StackTrace:
at Telerik.WinControls.UI.DayViewAppointmentsTable.appointment_MouseUp(Object sender, MouseEventArgs e)
   at Telerik.WinControls.UI.DayViewAppointmentsTable.AppointmentMouseUp(Object sender, MouseEventArgs e)
   at Telerik.WinControls.UI.RadSchedulerElement.scheduler_AppointmentElementMouseUp(Object sender, MouseEventArgs e)
   at Telerik.WinControls.UI.RadScheduler.OnAppointmentElementMouseUp(Object sender, MouseEventArgs args)...

1. Create a new project with RadScheduler.
2. Handle the AppointmentFormatting event and change appointment border color.
3. Run the project and add an appointment.

Currently RadScheduler sets the start date to be the first day of the current week in day view. RadScheduler should allow users to change this behavior in order to show the full month.

Check out the Weekly calendar style in Outlook

Resolution: 
In Q2 2014 we introduced new feature: WeeklyCalendarPrintStyle. More information you can find in our help: http://www.telerik.com/help/winforms/scheduler-print-support-schedulerprintstyle.html, section WeeklyCalendarStyle

Use GetMultiDayView().Intervals.Add method to add intervals in multi day view. Set the time to be 0:00.

drop a scheduler on a form and call it schMain. replace your form1 code with the code below. it will reproduce the issue. in the load event of the form, there's a method called BindForm. if you comment out this line, it works. the resources are all in color like they should be. if you put the line back in, it breaks and they all go gray. i attached screen shots of what i see too.
Comment: You should map the Color property of ResourceMappingInfo class to the respective property in your business object in order to solve this issue.

If an appointment is about to change its resource, e.NewResourceId in the AppointmentDropping event should return the id new the new appointment. However, it returns nothing.

1. Create a new project with RadScheduler.
2. Add some resources.
3. Set GroupType property to Resource.
4. Handle AppointmentDropping event and print its NewResourceId property.
4. Run the project and add an appointment.
5. Try to move this appointment to another resource.

The last row in RadScheduler's day view has different size than the others.

I found on you forum that someone else had this problem and was recommended to upgrade their printer driver. I upgraded mine and I have upd-pcl6-x64.5.6.0.14430 dated 12/15/2012 and it still fails.
The error I am getting is "The value '-1' is not a valid value for the enum 'PaperSourceKind'"

Can I set a default value for the paper source kind to get around this problem? If so, how do I set it? I tried to, but it's read only.

DECLINED: RadScheduler already supports saving/loading exceptions (set via the MasterEventId mapping property). The issue here seems to be in the database setup but the information provided is insufficient to reproduce the case. 

1) Create new reccuring appointment
2) Open some occurrence of created reccuring appointment
3) Change end date, click OK
Here will be first problem - reccuring on this occurence icon not changed (see attached screenshot).
4) Save data to DB
5) Try do delete saved occurence of reccuring appointment
6) Save data to DB
Here is the second problem - this will not delete.

Currently RadScheduler does not support binding to DataView objects.

DECLINED: This is a limitation of the DataSet model. The last section "Updating the database" of this help article http://www.telerik.com/help/winforms/scheduler-data-binding-data-binding-walkthrough.html explains how you can overcome this.

1. Create a new project with RadScheduler.
2. Follow the instructions in our sample-database example help article to create a sample database.
3. Set GroupType property to Resource.
4. Add some resources
5. Run the application, try to add some appointments and to save them.

1. Setup a new project with RadScheduler and bind it to a database.
2. Run the project and add an appointment.
3. Resize the appointment by dragging its bottom side down.

RadScheduler becomes slow when adding appointments with recurrence rule that affects large time periods (year for example)

Steps to reproduce:
1. Add a RadReminder component to a form
2. Set the StartNotificaton property to a TimeSpan of one hour and several minutes
3. Add a remind object to the reminder in a way that the time between now and the beginning of the appointment would be in the time interval between now and the now plus the reminder start notofication.
(e.g. this.radReminder1.StartNotification = new TimeSpan(1, 30, 0);
DateTime now = DateTime.Now;
this.radReminder1.AddRemindObject(new Appointment(now.AddMinutes(70), now.AddMinutes(90), "text"));

Start the project and show the reminder. You will see that the "Due in" time would not be correct.