Teams: Barebone support #106
Labels
No Label
Priority
Critical
Priority
High
Priority
Low
Priority
Normal
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Type
Breaking
Type
Bug
Type
Documentation
Type
Enhancement
Type
Feature
Type
Security
Type
Testing
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/extensions-website#106
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Bugs
Any team member should be able to edit any of the extensions.
If a user is removed from a team, we need to sanitize the database so that no extension they "exclusively" maintain still has the old Team selected.
Dropdown
draft_finalise
template, if the user is part of any Team, they must pick whether the extension should be part of any team.The form dropdown:
All this does is set (or not) the "Team" field for the extension.
All this does is set/unset the "Team" field for the extension.
Profile Settings
Button to "Leave Team" on the same line as the info.
Profile setting, show even when not part of a team.
Future tasks
Writing these down for reference (and in case someone from the community wants to help until it becomes a bigger priority).
If teams proves to be a useful feature, we will still need a way to:
Most front-end changes have been done or prepared from the tasklist on the new
teams-support
branch. As most tasks need back-end changes too to step further, I'm leaving the tasks unchecked for now.Back-end tasks are prepared with TODO: @back-end prefixed todos in templates to make them easier to find.