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

AY-6483_Choose Deadline pools with dropdown #29

Open
ynbot opened this issue Sep 3, 2024 · 2 comments
Open

AY-6483_Choose Deadline pools with dropdown #29

ynbot opened this issue Sep 3, 2024 · 2 comments
Assignees
Labels
sponsored This is directly sponsored by a client or community member type: enhancement Improvement of existing functionality or minor addition

Comments

@ynbot
Copy link
Contributor

ynbot commented Sep 3, 2024

Please describe the enhancement you have in mind and explain what the current shortcomings are?

publisher is allowing to set/override pools and groups, but user have to type them manually

this often leads to typos, wrong submissions and other issues

How would you imagine the implementation of the enhancemenet?

No response

Describe alternatives you've considered:

No response

Additional context:

link to discussion on Discord
(might be a private channel)

This issue was automatically created from Clickup ticket AY-6483

@ynbot ynbot added Enhancement sponsored This is directly sponsored by a client or community member labels Sep 3, 2024
@m-u-r-p-h-y m-u-r-p-h-y added type: enhancement Improvement of existing functionality or minor addition and removed Enhancement labels Sep 4, 2024
@jakubjezek001
Copy link
Member

Isn't this related to #5 ?

@BigRoy
Copy link
Contributor

BigRoy commented Sep 19, 2024

Isn't this related to #5 ?

It's related but not the same.

This issue is about changing the exposed fields to enum fields instead of text fields so that the user can pick the pools, machines, etc from the list of available. This also came up on the forum recently where I shared some images/logic that I have in my own fork because I do already have them as enum fields - however there are some limitations as stated on the forum.

The issue #5 is just about exposing those fields in the multiple integrations, because some hosts are not showing that pools field (that is currently a text field) yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sponsored This is directly sponsored by a client or community member type: enhancement Improvement of existing functionality or minor addition
Projects
None yet
Development

No branches or pull requests

5 participants