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

[BUG] Cannot select "All" nodes directly via the UI #134

Open
1 task done
surchs opened this issue Apr 16, 2024 · 1 comment
Open
1 task done

[BUG] Cannot select "All" nodes directly via the UI #134

surchs opened this issue Apr 16, 2024 · 1 comment
Labels
bug:ux Unexpected and unintended behavior that is detrimental to the user experience. _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again type:bug Defects in shipped code and fixes for those defects

Comments

@surchs
Copy link
Contributor

surchs commented Apr 16, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Expected Behavior

  • a specific node is selected
  • I'd rather search "All" nodes
  • I see "All" in the dropdown for nodes
  • I click on "All" in the node list

-> Now "All" should be selected

Current Behavior

tool_no_work_good

Clicking "All" in the node list doesn't do anything.
I can only get "All" by deselecting the last node.

Error message

user sad

Environment

No response

How to reproduce

see snippet

Anything else?

No response

@surchs surchs added type:bug Defects in shipped code and fixes for those defects bug:ux Unexpected and unintended behavior that is detrimental to the user experience. labels Apr 16, 2024
@surchs surchs changed the title [BUG] [BUG] Cannot select "All" nodes directly via the UI Apr 16, 2024
Copy link

github-actions bot commented Jul 1, 2024

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

  • prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
  • close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
  • archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
    apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
    label in the future. Use sparingly!

@github-actions github-actions bot added the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug:ux Unexpected and unintended behavior that is detrimental to the user experience. _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again type:bug Defects in shipped code and fixes for those defects
Projects
Status: No status
Development

No branches or pull requests

1 participant