cd-rite

Results 95 issues of cd-rite

In instances with a very large number of users, the current interface could get cumbersome. In actual user stories available now, STIGMan is being deployed in smaller, targeted instances where...

enhancement
UI

This could be accomplished via very thorough requests to API for individual reviews and their history, or by providing an API endpoint that can accept a search term, field, and...

enhancement
API
UI
OAS

For large collections, calls to: GET collections/{collectionId}/reviews could return very large result-set if no other parameters or filters are provided. Possible solutions: 1. Require at least one filter in the...

enhancement
API

Part of label validation code looks for collection Id in `assetFields.collectionId`, which is not set unless included in the request body. Need to use asset's current collection Id for label...

API

This issue is a WIP. Collection Grants are being reimplemented. The reimplementation will more clearly distinguish Collection Privileges and Collection Access. Collection Roles will enable sets of Collection Privileges, and...

API
UI
OAS

Replacement for Postman Collection, which has gotten unwieldy and hard to maintain. Being implemented directly with chai, chai-http, and mocha. Requirements: Easier to manage than Postman. Ability to run specific...

tests

User reported they transferred an asset from one collection to another. After transfer, UI panels that show labels in the destination collection would not render, due to columnFilter construction issue....

API
UI

This feature is intended for dev/test use only, and may be a bit of a trap for deployers who expect to be able to use it for backup purposes, etc.

API
UI

When a new benchmark is imported, metrics are recalculated, which can be a lengthy process for large deployments. No feedback is provided until recalculation is complete. This came to our...

API
UI

Error response: "error": "Bind parameters must not contain undefined. To pass SQL NULL specify JS null", We should supply a default value or make the field "required" in the OAS....

bug
API
OAS