Task relation keyboard shortcut doesn’t work after creating first task relation. #151

Closed
opened 2025-11-01 20:48:51 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @perfectra1n on GitHub (Aug 27, 2023).

Description

No response

Vikunja Frontend Version

0.21.0

Vikunja API Version

0.21.0

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

Originally created by @perfectra1n on GitHub (Aug 27, 2023). ### Description _No response_ ### Vikunja Frontend Version 0.21.0 ### Vikunja API Version 0.21.0 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_
Author
Owner

@kolaente commented on GitHub (Aug 27, 2023):

The relations are already shown at that point. What should the shortcut do instead?

@kolaente commented on GitHub (Aug 27, 2023): The relations are already shown at that point. What should the shortcut do instead?
Author
Owner

@perfectra1n commented on GitHub (Aug 27, 2023):

Hi @kolaente,

Understood, fair point. However since this is what happens after hitting r on a new task:
image

I was expecting this menu to open again after hitting r again, after assigning the first related task:
image

Since r is more or less "unbound" at that point since relations are already open, perhaps rebinding it to open the "New Task Relation" window wouldn't be too harmful?

@perfectra1n commented on GitHub (Aug 27, 2023): Hi @kolaente, Understood, fair point. However since this is what happens after hitting `r` on a new task: ![image](https://github.com/go-vikunja/frontend/assets/2390633/4f5e411a-0a39-4cc0-821d-45c1d5f3f203) I was expecting this menu to open again after hitting `r` again, after assigning the first related task: ![image](https://github.com/go-vikunja/frontend/assets/2390633/30edb5fb-42ab-4f1c-b99e-58b1c12803ef) Since `r` is more or less "unbound" at that point since relations are already open, perhaps rebinding it to open the "New Task Relation" window wouldn't be too harmful?
Author
Owner

@kolaente commented on GitHub (Aug 29, 2023):

Should be fixed with 5630c90dee - please check with the next unstable build if the solution works for you.

@kolaente commented on GitHub (Aug 29, 2023): Should be fixed with 5630c90dee647fedc6b937cc2fe46d0ddb2c24e4 - please check with the next unstable build if the solution works for you.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#151