Database models: Project and Issue #3

Open
opened 2019-11-10 01:26:58 +01:00 by binaryDiv · 0 comments
Owner

Stable-ish models for project and issues.

With release of v0.1.0 the models should be stable enough so that they may be extended easily but not fundamentally changed that often.

  • Model for Project:

    • Immutable numeric ID (not seen by users)
    • Unique project key (short upper case string that prefixes issue numbers, may be changed, but issue references must stay functional)
    • Project name
    • Owner (1 user)
    • Public/private (see #2)
  • Model for Issue

    • Immutable numeric ID (only for internal references)
    • Unique issue ID including project key (e.g. "TOFU-123")
    • When project key is changed, ID must change too, but old ID must still work and redirect to new ID
    • Issue title (short one line summary)
    • Issue description/text
    • Created date
    • Last modified date (?)
    • Creator (user)
    • Assignee (user)
    • Status (Backlog, To Do, In Progress, Done -- extendable!)
    • Resolution ("Fixed", "Won't fix", etc.)

Later:

  • Access Control Lists
  • Issue relations (X depends on Y, is caused by, Subtasks, ...)
  • and much more
Stable-ish models for project and issues. With release of v0.1.0 the models should be stable enough so that they may be extended easily but not fundamentally changed that often. - Model for Project: - Immutable numeric ID (not seen by users) - Unique project key (short upper case string that prefixes issue numbers, may be changed, but issue references must stay functional) - Project name - Owner (1 user) - Public/private (see #2) - Model for Issue - Immutable numeric ID (only for internal references) - Unique issue ID including project key (e.g. "TOFU-123") - When project key is changed, ID must change too, but old ID must still work and redirect to new ID - Issue title (short one line summary) - Issue description/text - Created date - Last modified date (?) - Creator (user) - Assignee (user) - Status (Backlog, To Do, In Progress, Done -- extendable!) - Resolution ("Fixed", "Won't fix", etc.) Later: - Access Control Lists - Issue relations (X depends on Y, is caused by, Subtasks, ...) - and much more
binaryDiv added the
Type: feature
Priority 2: high
Component: database
labels 2019-11-10 01:26:58 +01:00
binaryDiv added this to the Milestone 1: v0.1.0 milestone 2019-11-10 01:27:03 +01:00
This repo is archived. You cannot comment on issues.
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: binaryDiv/tofu#3
No description provided.