Feedback
Roadmap
Changelog

Have something to say?

Tell us how we could make the product more useful to you.

Completed

v5 API: label removal, story reordering and description updates return 200 but don't take effect

We automate our project against the v5 REST API with per-user API tokens, and we've hit three operations the API documents but doesn't appear to implement. In each case the request is accepted rather than rejected, so the failure is silent — a client that checks the status code concludes it worked. All three are in the Pivotal Tracker v5 spec that help.litetracker.com/api.html mirrors, and all three work correctly in your web UI, so this looks like a gap in the v5 layer rather than an intentional limitation. 1. Removing a label from a story — route not implemented (404) DELETE /services/v5/projects/{pid}/stories/{sid}/labels/{label_id} -> 404 DELETE /services/v5/projects/{pid}/labels/{label_id} -> 404 DELETE /services/v5/stories/{sid}/labels/{label_id} -> 404 The corresponding reads return 200, so the collections exist and it is the DELETE verb that is missing: GET /services/v5/projects/{pid}/stories/{sid}/labels -> 200 GET /services/v5/projects/{pid}/labels -> 200 Adding a label works as documented: POST /services/v5/projects/{pid}/stories/{sid}/labels with a nested label body -> 200. The practical effect is that every label our automation applies is permanent — a mistakenly applied label can never be cleared programmatically. 2. Removing a label via a story update — 200, no effect All of these return HTTP 200 with the label set unchanged on re-read: PUT /services/v5/projects/{pid}/stories/{sid} with "labels": [] PUT /services/v5/projects/{pid}/stories/{sid} with "label_ids": [] PUT /services/v5/projects/{pid}/stories/{sid} with "labels": [{"id": N}] PUT /services/v5/projects/{pid}/stories/{sid} with "story": {"labels": []} 3. Reordering a story — 200, no effect

Mack 21 days ago

1

Completed

Official MCP server for LiteTracker

I'd like to work with LiteTracker stories from AI coding tools (Claude Code, Cursor, etc.) without hand-rolling API calls. An official MCP server would make that a one-line setup instead of a bespoke integration per user. Concretely, the tools I'd want: - Search/list stories with the usual filters (project, state, label, owner, epic) - Read a story with its description, tasks, comments, blockers,and activity - Create and update stories — state, estimate, labels, owner - Add comments Why this should be cheap to build: the v5 REST API already exposes all of the above, so an MCP server is largely a thin typed wrapper over endpoints that exist today. Auth could reuse the existing X-TrackerToken API token. A remote/hosted MCP endpoint (OAuth, like Linear and Sentry ship) would be ideal, but a self-hostable stdio server would already be a big w

vernon@nitidbit.com about 1 month ago

1

Completed

Clicking on Story has a Clickbubble problem in Chrome for MacOS

On any of these items in MacOS I often can’t click on it. The item just “jiggles” a little bit up and down and then won’t open. Can’t hit Accept/Reject, can’t click the tickbox, can’t expand the task. Works fine on Windows, but I’m on latest Chrome, Latest MacOS and I suspect there’s some sort of a Z-index or click bubble issue or something. Anyone else seeing this?

Doug Bishop 4 months ago

1

Completed

Sorting broken

Hi team LT, The last week we have noticed increasingly unpredictable behaviour when sorting our items in the different panels. Up to a point where it currently is not workable (i.e. unable to indicate priority to team members due to sort failure). The problem appears to be restricted to certain panels in to our main project (#26f37a) which indeed contains many items (see screencast). We cannot reproduce it in a nearly-empty project. KR, Ammar.

Ammar Hamilcar Tijani 4 months ago

16

Completed

Epics and labels dissapeared for some tickets overnight

Today, we noticed that half of our tickets in backlog/icebox don’t have epics or labels assigned. I know that the labels/epics were there when I was going off yesterday afternoon. ProjectID: bdf14b In the rest of the projects, the labels disappear only for a smaller amount of tickets. Logout-login didn’t helped..

Michal Říha 5 months ago

Emails from same story should thread/group together

Related to this request: https://litetracker.featurebase.app/p/email-updates-clearer-action-and-story-title Now that I’ve used this feature, I realize because the subject line changes for each type of action, email readers cannot thread the messages. I.e. when someone works on a story, it goes through all the states (started, some comments, finished, delivered). Each email has a different subject. That means 4 or more emails per story. It would be great to have the 4 emails related to the same story be grouped together. That way, reviewing my email, I see the history of the story in one place instead of spread throughout my email inbox. I think this can be achieved by keeping only the story title in the subject line, and have the body of the email mention the action and details.

Winston 5 months ago

Completed

Viewing ticket by label and refreshing page leads to reordering Iteration/Backlog/Icebox

This one is very similar to my previous report with “My work” but currently. https://litetracker.featurebase.app/p/iteration-and-backlog-gets-temporary-reordered-when-viewing-my-work Steps to reproduce: Tap on any label on the ticket Column is displayed → label: “example” view Refresh the page Backlog and icebox are reorder by the label view. Viewing the tickets by label and refreshing the page leads to reordering Iteration/Backlog/Icebox

Michal Říha 5 months ago

3