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.

Sign up for GitHub

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

Jump to bottom

Secure option default values are not used by scheduled jobs #399

Closed
gschueler opened this issue May 16, 2013 · 1 comment
Closed

Secure option default values are not used by scheduled jobs #399

gschueler opened this issue May 16, 2013 · 1 comment
Assignees
@gschueler
Labels
bug
Milestone
1.5.3

Comments

@gschueler
Copy link
Member

If a job has a "secure" option with a default value that is required, the default value is not correctly used if the job is run via a cron schedule.
@ghost ghost assigned gschueler May 16, 2013
gschueler added a commit that referenced this issue May 16, 2013
@gschueler
Use defaults for secure options for scheduled jobs
2ca92e0 
* load defaults for the exposed secure options
* change job options to be loaded eagerly from db so that the quartz job
  doesn't fail to load them
* issue #399
@gschueler gschueler mentioned this issue Jun 26, 2013
Closed
@0x7aF777
Copy link

0x7aF777 commented Aug 23, 2018 •
edited
Loading

This bug occurs for me in version 2.6.6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gschueler gschueler

Labels
bug
Projects
None yet
Milestone
1.5.3
Development

No branches or pull requests
2 participants
@gschueler @0x7aF777