/
PreiseBlogAnmeldenKostenlos starten
Zurück zum Blog
Updates

Time & Budget for customers, all GitLab pipelines, and duplicating permission groups

Customers get a transparent Time & Budget overview with one-click approvals. Plus: every GitLab pipeline instead of only merge-request ones, duplicable permission groups, and status text on linked tickets.

Spedy Team3 min readAuf Deutsch lesen
Time & Budget for customers, all GitLab pipelines, and duplicating permission groups
#customers#budget#time-tracking#pipelines#gitlab#permissions

This update is mostly about more transparency for customers: a dedicated Time & Budget overview with one-click approvals. On top of that, every GitLab pipeline now shows instead of only merge-request ones, you can duplicate permission groups, and linked tickets show their status as text.


Time & Budget: the new customer overview

Customers want to know how much time is going into their project and where the budget stands — without the full staff view and all its individual entries. That now has its own page.

As a customer you find it in the sidebar under Time & Budget (route /time-budget). Per project it shows you:

  • Tracked time per ticket — bundled, so no individual entries and no per-day or per-user breakdown. Unconfirmed drafts (PENDING entries) are left out.
  • Budget status — spent and remaining, using the same numbers as the staff view.
  • Pending budget approvals — every waiting request with Approve and Reject ready to click. When rejecting, you can add an optional note for the team.

Pending approvals also surface right on the customer dashboard, so a sign-off doesn't get lost in the navigation.

The overview is protected by its own permission: View customer overview (customer-overview:view, category "Customer Overview"). Without it, the page and the menu entry stay hidden.


All GitLab pipelines — not just the ones with an open merge request

The Pipelines view only showed GitLab runs when they were attached to an open merge request. Pipelines on the default branch, on a branch without an open MR, on tags, or from schedules — the bulk of many projects — slipped through. Some repositories looked empty even though GitLab was building away.

That's fixed now: every GitLab pipeline appears in the view, whether or not there's an open merge request for it. A run now shows

  • the branch or tag and the trigger (e.g. push, tag, schedule),
  • a PR chip only when a merge request is actually linked.

The history gets more complete, too: the daily background sync now pulls in recent project pipelines, not just MR-scoped ones. So the view fills up even for repositories whose webhook was set up later.

Nothing changes for GitHub and Bitbucket — their runs appear as before.


Duplicating permission groups

Clicking a new group together from scratch when an existing one already almost fits was needlessly tedious. It's faster now.

Under Settings → Permission Groups, every group card gets a Duplicate action — including the read-only system groups. The copy

  • carries over permissions, description, color, and type,
  • gets an automatically unique name (with a numeric suffix on a name collision),
  • opens straight in the edit form so you can adjust it right away.

Members as well as the default and system status are not copied — the copy is always a fresh, editable custom group.


Linked tickets now show their status

Small but noticeable improvement: linked tickets used to show only a colored status dot — telling "Done" from "In Progress" was pure color-reading.

Now the status shows as text next to the dot (in the calm badge style: neutral text, color only via the dot). And the title is free to use the full row and is only shortened when there's genuinely no room left — instead of being hard-clipped at 200px. The read-only subtickets reuse the same badge, so links and subtickets read consistently.


In short

  • Time & Budget for customers at /time-budget: tracked time per ticket, budget status, and pending approvals with one-click Approve/Reject — unlocked by the customer-overview:view permission.
  • All GitLab pipelines now appear, not just merge-request ones — including branch/tag, trigger, and a more complete history.
  • Duplicate permission groups under Settings → Permission Groups, system groups included; the copy opens straight for editing.
  • Linked tickets and subtickets show their status as text and allow longer titles.

Frequently asked questions

Quick answers to the most common questions about this topic.

Where do customers find the new Time & Budget overview?
As a customer you find it in the sidebar under Time & Budget (route /time-budget). It shows, per project, the tracked time per ticket, the configured budget (spent/remaining), and every pending budget approval. The overview is unlocked by the View customer overview permission (customer-overview:view).
What do customers see in the Time & Budget overview — and what stays hidden?
Customers see tracked time bundled per ticket and the project's budget status (the same numbers as the staff view). Deliberately excluded are individual entries, per-day or per-user breakdowns, and unconfirmed drafts (PENDING entries).
Why didn't all GitLab pipelines show up before?
The Pipelines view only showed runs attached to an open merge request. Pipelines on the default branch, on branches without an open MR, on tags, or from schedules were dropped. Now every GitLab pipeline appears — the run shows its branch or tag and the trigger, with a PR chip only when a merge request is linked.
Can I duplicate a system permission group?
Yes. Under Settings → Permission Groups, every card — including the read-only system groups — now has a Duplicate action. The copy carries over permissions, description, color, and type, gets an automatically unique name, and opens straight in the edit form. Members and the default/system status are not copied.
What changed for linked tickets?
Linked tickets and subtickets previously showed only a colored status dot. Now the status appears as text next to it (e.g. "In Progress" instead of just a green dot), and the title is free to use the full row instead of being hard-clipped at 200px.
Time & Budget for customers, all GitLab pipelines, and duplicating permission groups | Spedy Blog