Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

mtg: Admin Rename with Rename reason, Admin log entry and mail

Open
  • Is something wrong?
#137 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
api, authentication, backend

Research direction

Start by reading services/mtg/GLOSSARY.md for the Rename and Admin log concepts, then trace the existing Self-Rename issue (#136) and the admin account page and endpoint. Map the endpoint, admin log, mail-gateway, HTTP tests, API spec generation, and i18n entry points. Done when all listed acceptance criteria pass, including locked accounts and refusing self-renames through the admin endpoint.

Written by the indexing model from the issue text.

Description

ready-for-agent

What to build

An Admin Renames another Account from the Account's page in the admin dashboard (see Rename, Admin log in services/mtg/GLOSSARY.md).

  • Same username rules and uniqueness check as the Self-Rename (#136).
  • A Rename reason is required and seen only by Admins.
  • Locked Accounts can be Renamed by an Admin.
  • Every Admin Rename writes one Admin log entry: acting Admin, affected Account's old username, the new username, when, and the reason. The admin log table shows it.
  • The Account is mailed its new username (without the reason) through the mail-gateway, since Login and recovery both need the username. This deliberately differs from Lock, which sends no mail.
  • The admin dashboard hides the action on the Admin's own Account and the backend refuses it there; Admins Rename themselves through the Self-Rename.
  • No rename cli subcommand.

Acceptance criteria

  • Admin Renames another Account, including a locked one; the Account can log in with the new username
  • Missing reason is refused
  • Taken or invalid username is refused
  • Admin log entry records old and new username and the reason; shown in the admin log table
  • Mail with the new username goes to the Account's email, without the reason
  • Rename of the Admin's own Account via the admin endpoint is refused; the UI hides the action there
  • Non-Admins cannot use the endpoint
  • Migration for the new Admin log action committed; HTTP tests cover the cases above; API spec and client regenerated; i18n keys added
Dominant language
TypeScript
Stars
0
Forks
1
Avg merge
14h 36m
Merged PRs (30d)
24

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from myOmikron/code

All issues in myOmikron/code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.