Skip to content

Feature Request: Customizable UI Terminology for "Team" and "Group" #513

Closed as not planned

Description

@HishamHR5

Currently, the application hardcodes the terminology "Team" and "Group" throughout the user interface (e.g., "Filter by Teams", "Team Group Filter", "Team Profile", "Download team progress").

While "Team" and "Group" work well for many organizations, other adopters of the DSOMM dashboard may organize their software lifecycle differently and might prefer terminology like "App" and "Portfolio", or "Client" and "Industry".

We should allow users to customize these display labels via the Settings menu so the application's vocabulary can match their organizational structure.

Note: Data structures (e.g., YAML teams keys) should remain unchanged to minimize friction. This is purely a UI presentation change.

Acceptance Criteria:
-Users can enter custom terms for "Team" and "Group" in the Settings page.
-Changing these terms dynamically updates UI headers, filters, and buttons across all relevant pages (e.g., Circular Heatmap, Mapping, Reports).
-If no custom term is set, the application continues to default to "Team" and "Group".

Activity

  1. HishamHR5 commented on Mar 18, 2026

    @HishamHR5
    ContributorAuthor

    Hey @vbakke , @wurstbrot
    This is my proposed change

    -In Settings: Introduce custom text inputs for teamLabel and groupLabel in the Settings page and store the values in localStorage.
    -Dynamic UI Rendering: Inject these new labels (with defaults of "Team" and "Group") into all UI component headers, tooltips, and buttons that currently have those words hardcoded.
    -Preserve Data Structures: Ensure backend metrics and data schemas representing teams map transparently to these new visual names.

  2. vbakke commented on Mar 22, 2026

    @vbakke
    Collaborator

    Thank you @HishamHR5, your proposal looks good. I have assigned this issue to you.

    Make sure you include the messages and popup dialogs as well. They are easily missed : )

  3. HishamHR5 commented on Mar 27, 2026

    @HishamHR5
    ContributorAuthor

    Hey @vbakke, @wurstbrot 👋

    I've pushed the PR for issue #513

    I made sure to cover the messages and popup dialogs as well, per your note @vbakke :

    Would appreciate it if you could take a look when you get a chance.
    Happy to address any feedback!

  4. linked a pull request that will close this issuefeat: customizable UI terminology 513 #517on Mar 28, 2026
  5. github-actions commented on May 2, 2026

    @github-actions

    This issue has been automatically marked as stale because it has not had recent activity. 📆 It will be closed automatically in one week if no further activity occurs.

  6. github-actions commented on May 9, 2026

    @github-actions

    This issue was closed because it has been stalled for 7 days with no activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions