github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-03-09 07:13:35 -05:00
Code Issues 219 Packages Projects Releases 2 Wiki Activity

"Save" copy instead of "Done" for Description #12

New Issue
Closed
opened 2025-11-01 20:44:00 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-01 20:44:00 -05:00
Owner
Copy Link

Originally created by @jbd7 on GitHub (Aug 18, 2021).

Hey, I noticed a minor UX inconsistency today:

  • While editing a task description on the List-view, the save button is called "Save" and has a blue background.
  • While editing a task description on the Task-view, the save button is called "Done" and has a grey background.

There's also proximity with the green "Done" status button. By mistake I marked a task as Done instead of saving the description.

image

Suggestion: Keep the copy "Save" and the blue button background consistent through the frontend.

Originally created by @jbd7 on GitHub (Aug 18, 2021). Hey, I noticed a minor UX inconsistency today: - While editing a task description on the List-view, the save button is called "Save" and has a blue background. - While editing a task description on the Task-view, the save button is called "Done" and has a grey background. There's also proximity with the green "Done" status button. By mistake I marked a task as Done instead of saving the description. ![image](https://user-images.githubusercontent.com/13196991/129921509-f4c1393d-8409-447d-ab98-0b36a0b629aa.png) Suggestion: Keep the copy "Save" and the blue button background consistent through the frontend.
GiteaMirror commented 2025-11-01 20:44:01 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Aug 18, 2021):

There's been a bit of discussion about that lately: https://kolaente.dev/vikunja/frontend/issues/652

In comparison to the save button on the quick edit this one only saves the description whereas the done button only saves the description. In the latest unstable version the done button has been moved below the text, similar to the way it is solved in comments. Please check it out on try, what do you think?

@kolaente commented on GitHub (Aug 18, 2021): There's been a bit of discussion about that lately: https://kolaente.dev/vikunja/frontend/issues/652 In comparison to the save button on the quick edit this one only saves the description whereas the done button only saves the description. In the latest unstable version the done button has been moved below the text, similar to the way it is solved in comments. Please check it out on try, what do you think?
GiteaMirror commented 2025-11-01 20:44:01 -05:00
Author
Owner
Copy Link

@jbd7 commented on GitHub (Aug 18, 2021):

Thanks, I didn't see that. Btw, do you prefer threads on koalente.dev instead of github?

From the screenshots there the placement does look better. It'd indeed make sense to keep consistency with the "COMMENT" button just blow. When it comes to the copy, I think "Edit"/"Save" or "Edit"/"Update" is more common and understood than < Pencil-icon >/"Finish", taking as an example this very github page :)
image

@jbd7 commented on GitHub (Aug 18, 2021): Thanks, I didn't see that. Btw, do you prefer threads on koalente.dev instead of github? From the screenshots there the placement does look better. It'd indeed make sense to keep consistency with the "COMMENT" button just blow. When it comes to the copy, I think "Edit"/"Save" or "Edit"/"Update" is more common and understood than < Pencil-icon >/"Finish", taking as an example this very github page :) ![image](https://user-images.githubusercontent.com/13196991/129925500-460593f6-7b04-4066-96ee-ca94e6882406.png)
GiteaMirror commented 2025-11-01 20:44:01 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Aug 18, 2021):

Threads on Gitea or here are both fine for me. The majority of the active development happens the Gitea instance though.

I agree with you about the wording, will put something up.

@kolaente commented on GitHub (Aug 18, 2021): Threads on Gitea or here are both fine for me. The majority of the active development happens the Gitea instance though. I agree with you about the wording, will put something up.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/caldav
area/filters
area/frontend
area/gantt
area/internal-code
area/typesense
bug
changes requested
confirmed
dependencies
enhancement
good first issue
help wanted
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#12
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?