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

Multi-value options not pre-populated when doing a "run again" #346

Closed
andysteady opened this issue Apr 2, 2013 · 3 comments
Closed

Multi-value options not pre-populated when doing a "run again" #346

andysteady opened this issue Apr 2, 2013 · 3 comments
Labels
Milestone

Comments

@andysteady
Copy link

When you do a "run again" for a job with some multi-value options, the values of multi-value options (lists) are not pre-populated as all the other values are.

@gschueler
Copy link
Member

Hi Andy,

I'm trying to reproduce this, but don't seem to have the same problem.

Do you have an example job.xml that you can send that exhibits the behavior? Also, what Web browser, version, OS etc are you using. Perhaps it is a javascript/browser issue.

@andysteady
Copy link
Author

Hi,
I will email you a job by private email but it happens on all my jobs on both chrome and firefox on ubuntu precise.
Cheers,
Andy

@gschueler
Copy link
Member

thanks for the testable job.xml, the bug turns out to happen if the multi-value option doesn't have any pre-defined allowed-values. in that case it will fail to load the previously used values when presenting the execution form.

so, if you need a workaround, you can define a value under "Allowed Values: List" for the option if possible.

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

No branches or pull requests

2 participants