Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

E1654. Improve date-picker and deadlines #760

Closed
wants to merge 86 commits into from

Conversation

DJaySathe
Copy link
Contributor

What it does: allow instructor to define deadlines such as the assignment, peer review.
What’s wrong with it:
The current date picker doesn't let you change dates easily. Unless you spell the deadline out to the minute, it changes the deadline to the current time!
When doing testing, we very often want to test an assignment in, say, the submission or review phase, even after the assignment is complete. In order to do this, we need to change several due dates from the UI. It would be a lot easier if we just had a command that said, "set all due dates ahead by x days.
What needs to be done:
Replace the date time picker in _due_dates.html.erb
Find a more user friendly JQuery datetime picker that support time zones and allow users to define deadline by date and time (hour).
Allow the user to change the timezone, but try guess the appropriate timezone for each entry. E.g., set the default time zone to the same timezone as the owner/instructor of the course.
Allow users to set all due dates ahead by x days, and the algorithm calculates the exact date and time

@coveralls
Copy link

Coverage Status

Coverage increased (+19.5%) to 42.54% when pulling d442099 on DJaySathe:master into d70cfe0 on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+19.4%) to 42.469% when pulling d442099 on DJaySathe:master into d70cfe0 on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+19.4%) to 42.469% when pulling d442099 on DJaySathe:master into d70cfe0 on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+19.5%) to 42.54% when pulling d442099 on DJaySathe:master into d70cfe0 on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+19.5%) to 42.54% when pulling d442099 on DJaySathe:master into d70cfe0 on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+19.5%) to 42.54% when pulling d442099 on DJaySathe:master into d70cfe0 on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+19.4%) to 42.469% when pulling d442099 on DJaySathe:master into d70cfe0 on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+19.4%) to 42.469% when pulling d442099 on DJaySathe:master into d70cfe0 on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+19.5%) to 42.54% when pulling d442099 on DJaySathe:master into d70cfe0 on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+19.5%) to 42.54% when pulling d442099 on DJaySathe:master into d70cfe0 on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+19.5%) to 42.54% when pulling d442099 on DJaySathe:master into d70cfe0 on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.07%) to 42.469% when pulling 25e4959 on DJaySathe:master into 4ee1f91 on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 42.54% when pulling 171c9be on DJaySathe:master into 4ee1f91 on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 42.54% when pulling 98cdb3c on DJaySathe:master into 4ee1f91 on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 42.54% when pulling 98cdb3c on DJaySathe:master into 4ee1f91 on expertiza:master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.005%) to 42.546% when pulling 92e366a on DJaySathe:master into 4ee1f91 on expertiza:master.

@yangsong8
Copy link
Contributor

I believe this is duplicated.

@yangsong8 yangsong8 closed this Nov 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants