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

QM should be able to restrict ordering of high-risk items to require QM approval #7838

Open
Saakra opened this issue Apr 28, 2022 · 1 comment · May be fixed by #34755
Open

QM should be able to restrict ordering of high-risk items to require QM approval #7838

Saakra opened this issue Apr 28, 2022 · 1 comment · May be fixed by #34755
Labels
D2: Medium Difficulty: A good amount of codebase knowledge required. P3: Standard Priority: Default priority for repository items. T: New Feature Type: New feature or content, or extending existing content

Comments

@Saakra
Copy link
Contributor

Saakra commented Apr 28, 2022

Description

Most rounds, at least one person in cargo randomly orders weapons, armor, or other high-risk items. QM should be able to put restrictions on specific orders by a security/cost basis to require QM approval

Screenshots

Additional context

@Peptide90
Copy link
Contributor

Agreed. Related to #7836

We need more control over the cargo ordering system to allow access level approvals of order (QM, Departments, Heads etc) as well as potentially to allow events to play into it e.g. Shortage of X, ordering of Y is disabled for Z time.

@Peptide90 Peptide90 added P3: Standard Priority: Default priority for repository items. T: New Feature Type: New feature or content, or extending existing content D2: Medium Difficulty: A good amount of codebase knowledge required. labels Apr 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
D2: Medium Difficulty: A good amount of codebase knowledge required. P3: Standard Priority: Default priority for repository items. T: New Feature Type: New feature or content, or extending existing content
Projects
None yet
2 participants