Requesting Features

Have an idea for a new feature? If so, please carefully follow these steps:

Step 1: Check for an existing request

There are over 100 existing feature requests. Someone else probably already wants what you want. Please search through the issue tracker (link below) and if you find what you’re looking for, please vote with a thumbsup reaction on the topmost description of the issue (learn how) and press the Subscribe button to receive updates when progress is made.

Comments like “+1” or “when will this be done?” will be ignored. Only thumbsup reactions on the topmost description will be counted.

See all feature requests ranked by demand »
(powered by ghi-scoreboard)

Step 2: Is it a valid feature?

Ask yourself, is this a feature other people would find useful? Often times the feature you want built is too specific to your application and not generalizable enough for others.

Also, is it within the scope of the FullCalendar project? FullCalendar is a front-end widget for displaying events, so any sort of back-end-related feature requests (PHP, MySQL,, etc) are out of scope.

Step 3: Describe the feature

Please write a detailed description of the feature. Please explain why the feature would be useful and how it might be implemented. Assume the reader knows very little about your situation and explain everything.

For user-interface features, please include mockups of what you want it to look like.

For API improvements, such as new options or methods, please write some example code of how one might use it.

Step 4: Use the issue tracker

If you are confident you have followed all the above steps, enter your feature request into the appropriate issue tracker:

Please enter only one feature request per issue and do not combine issues.