{"action":"closed","issue":{"url":"https://api.github.com/repos/dangrossman/bootstrap-daterangepicker/issues/822","labels_url":"https://api.github.com/repos/dangrossman/bootstrap-daterangepicker/issues/822/labels{/name}","comments_url":"https://api.github.com/repos/dangrossman/bootstrap-daterangepicker/issues/822/comments","events_url":"https://api.github.com/repos/dangrossman/bootstrap-daterangepicker/issues/822/events","html_url":"https://github.com/dangrossman/bootstrap-daterangepicker/issues/822","id":109965294,"number":822,"title":"\"Dedicated\" calendar","user":{"login":"margielm","id":684828,"avatar_url":"https://avatars.githubusercontent.com/u/684828?v=3","gravatar_id":"","url":"https://api.github.com/users/margielm","html_url":"https://github.com/margielm","followers_url":"https://api.github.com/users/margielm/followers","following_url":"https://api.github.com/users/margielm/following{/other_user}","gists_url":"https://api.github.com/users/margielm/gists{/gist_id}","starred_url":"https://api.github.com/users/margielm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/margielm/subscriptions","organizations_url":"https://api.github.com/users/margielm/orgs","repos_url":"https://api.github.com/users/margielm/repos","events_url":"https://api.github.com/users/margielm/events{/privacy}","received_events_url":"https://api.github.com/users/margielm/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-10-06T09:05:51Z","updated_at":"2015-10-06T12:21:16Z","closed_at":"2015-10-06T12:21:16Z","body":"Cool feature in line 1.x is that first calendar is dedicated to \"start date\" and second to \"end date\". in version 2.x looks like it has change. Both calendars are for start  and end dates and which date one is selecting is based on \"order of clicking\". I.e. first click is always \"start\" second always \"ends\".\r\nThis is very cumbersome one one wants to change one date only. User has to ALWAYS reset both ends of the range.\r\nIs this a future or a bug? is there any option to rollback to 1.x behaviour? "}}