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

Inconvenient choice of job exclusive flag in Job Meta json schema #153

Open
moebiusband73 opened this issue Jun 20, 2023 · 0 comments
Open
Labels
backend backend API related issues enhancement New feature or request frontend Svelte UI related issues

Comments

@moebiusband73
Copy link
Member

Currently the exclusive integer flag has the following allowed values: 0 - Shared among multiple jobs of multiple users, 1 - Job exclusive, 2 - Shared among multiple jobs of same user.
For tests it would be more convenient if 0 would mean exclusive job and >0 shared job.
Proposal for change:
0 - Job exclusive
1 - Shared among multiple jobs of same user
2 - Shared among multiple jobs of multiple users

@moebiusband73 moebiusband73 added enhancement New feature or request frontend Svelte UI related issues backend backend API related issues labels Jun 20, 2023
@moebiusband73 moebiusband73 added this to the Release v1.3.0 milestone Oct 11, 2023
@moebiusband73 moebiusband73 removed this from the Release v1.3.0 milestone Mar 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend backend API related issues enhancement New feature or request frontend Svelte UI related issues
Projects
None yet
Development

No branches or pull requests

1 participant