Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Create API Endpoint(s) to CRUD Record Contribution Criteria Configuration

Description

Purpose/Overview:

Provide API endpoints to CRUD record contribution criteria configurations for the local server-central server pair to be used by front-end UI and other API clients via OKAPI.

Requirements/Scope:

  1. Requirement: Provide API endpoint(s) to CRUD record contribution criteria configuration objects for central servers

  2. Requirement: Should be restricted by configuration-specific logical permissions

    • All permissions

    • View-only

    • View, create, edit

Approach:

Acceptance criteria:

  • AC: Users with appropriate permissions:

    • AC: Can POST to create a new configuration

    • AC: Can PUT to update an existing configuration

    • AC: Can GET to retrieve an existing configuration

    • AC: Can DELETE to drop existing configuration

    • AC: Can GET to query for existing configurations

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Brooks TravisJune 1, 2021 at 6:10 AM

 Probably not beyond the query by ID that's done to retrieve an existing configuration.

Andrii ShapovalovJune 1, 2021 at 3:37 AM

Contribution Criteria Configuration, according to has no name and one per Central Server. So it is a complex attribute of Central Server which contains contribution rules only. Does it really need to follow to this requirement: "AC: Can GET to query for existing configurations"?

 

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Volaris

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created April 25, 2021 at 9:12 PM
Updated September 17, 2021 at 11:19 AM
Resolved July 6, 2021 at 7:35 AM
TestRail: Cases
TestRail: Runs