Functional overview
All the possible card fields should be represented on the card:
- int field
- float field
- computed field
- string field
- text field (when HTML format, tags are stripped)
- Date fields (human format "A day ago" with the real date on hover)
- List fields bound to static values (with the values' colors). Value colors can be "legacy RGB" or "tlp" (CSS classname)
- List fields bound to users (with the user's avatar)
- Shared fields (same as lists)
- Open lists (same as lists)
- Cross-references field
- File field (attachments). It should be a link to attached files (no preview)
- Permissions on artifact (just list the user groups separated by commas)
- Read-only fields: artifact id, per-tracker id, priority, Last update date, Submitted on
- Last updated by, Submitted by
Technical overview
At the design level, the card fields display should match that of Kanban or planning v2. On the technical level, code has to be rewritten because Kanban and planning use an AngularJS module (service / directive).
Card fields information should be added in REST routes (see Agiledashboard routes for reference)