-
Notifications
You must be signed in to change notification settings - Fork 615
[BUG]: Teams - Team visibility updates are not reflected until the page is refreshed #2691
Copy link
Copy link
Labels
SHOULDP2: Important but not vital; high-value items that are not crucial for the immediate releaseP2: Important but not vital; high-value items that are not crucial for the immediate releasebugSomething isn't workingSomething isn't working
Milestone
Description
🐞 Bug Summary
Teams - Team visibility updates are not reflected until the page is refreshed
🧩 Affected Component
Select the area of the project impacted:
-
mcpgateway- API -
mcpgateway- UI (admin panel) -
mcpgateway.wrapper- stdio wrapper - Federation or Transports
- CLI, Makefiles, or shell scripts
- Container setup (Docker/Podman/Compose)
- Other (explain below)
🔁 Steps to Reproduce
- Go to http://localhost:8080/admin/#teams.
- Click on "Edit Settings" of any team.
- Go to "Visibility" drop-down and choose a different visibility than the current one.
- Click on "Update Team" button.
🤔 Results
The user is returned to the My Teams screen, but the updated visibility of that specific team is not reflected until the page is refreshed.
🤔 Expected Behavior
After the visibility is updated, the change is also reflected on the My Teams screen.
📓 Logs / Error Output
Paste any relevant stack traces or logs here.
🧠 Environment Info
You can retrieve most of this from the /version endpoint.
| Key | Value |
|---|---|
| Version or commit | 6d65f45 |
| Runtime | Python 3.11.14 |
| Platform / OS | macOS |
| Container | none |
🧩 Additional Context (optional)
Add any configuration details, flags, or related issues.
Related to #2663
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
SHOULDP2: Important but not vital; high-value items that are not crucial for the immediate releaseP2: Important but not vital; high-value items that are not crucial for the immediate releasebugSomething isn't workingSomething isn't working