nextcloud / nextcloud/contacts

Add a "Rank" field.

Open
#3,887 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement
Dominant language
JavaScript
Stars
642
Forks
220
Avg merge
14h 39m
Merged PRs (30d)
51

Description

Is your feature request related to a problem? Please describe.

Although knowing someone's profession is useful for people using their contacts as CRM, I frequently need to know someone's profession alongside their rank, with the rank generally more important. Not having these attributes separated is a significant problem for me, because it leads to me placing them sometimes in the notes (if the name of the profession is long) or bracketed, alongside the profession otherwise.

Describe the solution you'd like

A separate "rank" field.

Describe alternatives you've considered

https://help.nextcloud.com/t/suggestion-adding-custom-attributes-to-contacts-programatically/21046/9?u=rokejulianlockhart#:~:text=How%20do%20you,being%20per-contact

Additional context

As https://en.wikipedia.org/w/index.php?title=Ranks_and_insignia_of_NATO&oldid=1218198237#Comparison_to_US_system:~:text=Rank%20group,Officer%20candidate%2FCadet explains, I want to utilize NATO STANAG 2116 values: OR-0/9 or OF-0/10 (although I wouldn't want it restricted to this, because I use OR-0 and OF-0 unofficially to refer to trainees).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by tracing how contact professions are represented and edited, then determine where a separate Rank field belongs and how its values should be handled. Done means contacts support a distinct rank alongside profession without restricting the requested rank values.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
full-stack
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.