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

Move "Time limit per task" above the "Advanced" button #18

Open
mbernst opened this issue Dec 14, 2017 · 1 comment · May be fixed by crowdresearch/daemo#1047
Open

Move "Time limit per task" above the "Advanced" button #18

mbernst opened this issue Dec 14, 2017 · 1 comment · May be fixed by crowdresearch/daemo#1047
Assignees

Comments

@mbernst
Copy link

mbernst commented Dec 14, 2017

Design critique: right now the Advanced button in authoring is not at the bottom, and the "Time limit per task" field gets flung around as the Advanced section is opened and closed:

screen shot 2017-12-14 at 12 19 37 pm

screen shot 2017-12-14 at 12 19 52 pm

This causes confusion about where to find it.

Right now I think the source of the problem is that Daemo hasn't made a clear decision about whether time limit is Advanced — in which case it should be always hidden in Advanced — or so common that it should be shown and editable always.

My proposal

I propose we move it entirely within the Advanced section.

Why? I'm aiming for the 80/20 rule here. How often do people need to adjust the length of time a task can be checked out? If the default were short, I would think that people would need to change it all the time, and it should be always visible. But, the default is 8 hours, which is much longer than any task anyone's ever put on our platform. Moreover, because workers can only have one task per project checked out at once, there's less hoarding, so we don't need to have long time limits to allow workers to do so. All this leads me to a conclusion that the time limit shouldn't be visible except in Advanced.

So the revised design would be the same when Advanced is expanded:
screen shot 2017-12-14 at 12 19 52 pm

And remove the summary when Advanced is collapsed:
screen shot 2017-12-14 at 12 25 57 pm


Use comments to share your response or use emoji 👍 to show your support. To officially join in, add yourself as an assignee to the proposal. To break consensus, comment using this template. To find out more about this process, read the how-to.

@mbernst mbernst self-assigned this Dec 14, 2017
@mbernst
Copy link
Author

mbernst commented Dec 21, 2017

Summary

No discussion, so executed as proposed.


As per discussion today, the goal moving forward will be to have this summary prior to the weekly meeting, so everyone knows what has been agreed upon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants