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

As a user, when creating/modifying a SCHEDULED and DEADLINE timestamp, I want to see more semantic information in the modal #217

Closed
aspiers opened this issue Jan 8, 2020 · 8 comments
Assignees
Labels
enhancement New feature or request

Comments

@aspiers
Copy link

aspiers commented Jan 8, 2020

(This is a minor UI/UX bug, but when combined with #218 it becomes a slightly more significant problem.)

If I click either of the new DEADLINE or SCHEDULED icons, I get an identical-looking modal dialog with no way to tell which type of timestamp I'm editing. They should say "Edit scheduled timestamp" and "Edit deadline" or similar to differentiate the two.

This is particularly important given that currently the two icons are very similar and it's not immediately obvious which is which. I've filed #218 to track that separate but related issue.

@schoettl
Copy link
Collaborator

schoettl commented Jan 8, 2020

Good point, this was also on my list.

Maybe we can make the title of the modal a property and pass an appropriate value for it.

There must be a third option "Edit timestamp" for normal timestamps in title or description.

We could also differentiate between "Add deadline" and "Edit deadline", to make clear that there was no deadline before.

@munen munen changed the title SCHEDULED and DEADLINE modal dialogs are identical As a user, when creating/modifying a SCHEDULED and DEADLINE timestamp, I want to see more semantic information in the modal Jan 9, 2020
@munen munen added enhancement New feature or request and removed bug Something isn't working labels Jan 9, 2020
@munen
Copy link
Collaborator

munen commented Jan 9, 2020

@aspiers @schoettl Does either of you want to work on this?

One note I want to make: Currently, it's always "edit timestamp", never "create timestamp". Rationale: As soon as you hit the action button, you'll have a corresponding timestamp for today. In the modal, you can change the date or delete the timestamp altogether.

It would be possible to change this behavior, but that would not be trivial - even from a UX standpoint, because it would require more clicks to set a simple timestamp.

Hence, I propose to keep this issue to differenciate between 'schedule' and timestamp' in the modal header.

PS: This is not a bug according to the contributor guidelines: https://github.com/200ok-ch/organice/blob/master/CONTRIBUTING.org#did-you-find-a-bug-or-do-you-want-to-implement-a-new-feature

@aspiers
Copy link
Author

aspiers commented Jan 9, 2020

@munen commented on January 9, 2020 10:41 AM:

@aspiers @schoettl Does either of you want to work on this?

One note I want to make: Currently, it's always "edit timestamp", never "create timestamp". Rationale: As soon as you hit the action button, you'll have a corresponding timestamp for today. In the modal, you can change the date or delete the timestamp altogether.

It would be possible to change this behavior, but that would not be trivial - even from a UX standpoint, because it would require more clicks to set a simple timestamp.

Makes sense.

Hence, I propose to keep this issue to differenciate between 'schedule' and timestamp' in the modal header.

Thanks - that was my original intention.

PS: This is not a bug according to the contributor guidelines: /CONTRIBUTING.org@master#did-you-find-a-bug-or-do-you-want-to-implement-a-new-feature

OK. There's a certain degree of subjectivity here - personally when I encounter something for which the UI/UX is not optimal, I tend to think of it as a minor UI/UX bug, but I agree it also makes sense to think of it as an enhancement.

However in this case I think it's fair to say that fixing this issue would be an enhancement but would not be an implementation of a new feature. And the section header you link to and https://github.com/200ok-ch/organice/issues/new/choose both present a binary choice between "bug" and "feature request", so neither of them currently cater in an optimal way to filing enhancements for existing features. I would have happily applied the enhancement label when filing this rather than bug, if that option had been presented to me, but it wasn't. So I think there's room for improvement in both the contributor guidelines and the issue templates.

@schoettl
Copy link
Collaborator

schoettl commented Jan 9, 2020

I would try to implement that. I assigned me for this issue.

@schoettl schoettl self-assigned this Jan 9, 2020
@munen
Copy link
Collaborator

munen commented Jan 9, 2020

@schoettl 👍

@munen
Copy link
Collaborator

munen commented Jun 27, 2022

We have a distinction between "edit deadline" and "edit schedule" since merging #751, but forgot to close the issue.

Thank you, @aspiers, for the initial report 🙏

image

@munen munen closed this as completed Jun 27, 2022
@aspiers
Copy link
Author

aspiers commented Jun 27, 2022

Fantastic, thanks @munen! I hope to get back to using organice sometime this summer. And I would also love to come on a coding/meditation retreat sometime too ;-)

@munen
Copy link
Collaborator

munen commented Jun 27, 2022

@aspiers There's a lot of work going into organice lately and way more to come^^ Maybe there's something in there that you will enjoy^^

As for joining for a retreat or coding templestay, let me know anytime! 👍

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants