Skip to content

New model for storing project types in the database #87

Closed
@vikasrohit

Description

@vikasrohit

Till date we are maintaining the project types (aka categories) in JSON mapping in each project we need it. Now we are moving it to the database to make all services independent of keeping them in sync for this JSON mapping.

Requirements:

  1. New model ProjectType backed by table project_types with only two fields key and displayName
  2. Simple CRUD operations on top of it
    1. GET /v4/projectTypes to list all available project types (no filtering and no sorting)
    2. GET /v4/projectTypes/{key} to fetch specific project type details
    3. POST /v4/projectTypes to create new project type
    4. PATCH /v4/projectTypes/{key} to update existing project type
    5. DELETE /v4/projectTypes/{key} to delete existing project type
  3. Only users with administrator or Connect Admin roles should be able to allow create new project type or update/delete existing one.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions