Add Person and Status field types
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript
- Domain
- full-stack
Research direction
The issue names no files, tests, or entry points; start by tracing existing field types, per-field configuration, row metadata, board grouping, and filter/sort implementations. Done means both field types can be configured and used on rows, Status grouping works in the board, and filtering and sorting work for Person and Status.
Written by the indexing model from the issue text.
Description
Goal
Two field types Cortext doesn't have today. Person stores one or more WP user references per row (Assignee, Reviewer, Reporter, and so on). Status is a select-with-workflow-groups, which is what board grouping actually wants.
Scope
- Person field type:
- Stores one or more WP user IDs in row meta.
- A picker UI that searches WP users by display name.
- Single or multi configurable per field.
- Renders as user chips with avatar.
- Status field type:
- Select-style options grouped into workflow buckets ("To-do", "In progress", "Done"), configurable per field.
- Default groups so new fields ship with sensible workflows.
- The board layout groups by Status's workflow buckets when Status is the chosen group-by field.
- Filter and sort on Person (by user) and Status (by group, by option).
- Status workflow groups and Person's single/multi setting are managed from the per-field config panel.
Out of scope
- Notification on assignment.
- Permissions tied to Person fields.
- Workspace user directory beyond WP users.
Acceptance criteria
- You can add a Person field, configure single or multi, and assign WP users to rows.
- You can add a Status field with custom groups; rows pick a status from any group.
- The board layout grouped by Status uses the workflow buckets.
- Filter and sort work on both types.
- Dominant language
- JavaScript
- Stars
- 51
- Forks
- 2
- Avg merge
- 17m
- Merged PRs (30d)
- 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Automattic/cortext
-
area: publishing priority: medium type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Automattic/cortext#427 ·
-
area: canvas type: code quality
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/cortext#304 ·
-
area: desktop area: distribution priority: medium type: enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
Automattic/cortext#446 ·
-
area: collections area: shell priority: medium type: enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
Automattic/cortext#445 ·
-
area: desktop area: sync priority: high type: enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
Automattic/cortext#444 ·
All issues in Automattic/cortext
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·