Subteam rename permission issue
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Here's the scenario...
1 - Create a team;
2 - Create a subteam;
3 - Add members to the subteam;
4 - Rename the subteam;
5 - Members of the subteam don't have access/permissions to post again, yet the renamed subteam shows the correct number of members.
This is the message shown on the Keybase app:
If another subteam admin tries to rename the subteam back to the original name, that admin receives an error even if has full permissions:
Renaming the subteam back to its original name fixes everything. In other words, renaming of subteams isn't working, the only solution to have a subteam with a different name is to create it from scratch.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reproducing the listed team and subteam creation, membership, and rename steps in the Keybase app, then compare posting access and rename behavior before and after the rename. Done means subteam members retain permission to post after renaming and an authorized admin can rename the subteam without the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authorization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100