Backlog

Next up

In Progress

Done

Main Roadmap

In the immediate term, a CSV export feature would be a means to verify that a Pivotal Tracker project was imported correctly; longer-term, the ability to get data out of any Web service is essential as a mitigation for the risks of data loss that come with using any Web service.

In Review

CSV Export

Jonathan Lovelace

Pivotal Tracker has a useful feature that allows the user to temporarily, only in the current session in the current window, view the backlog as if the velocity were some user-specified value. This is invoked by clicking on the current-velocity element in the header of the backlog or current-iteration-and-backlog panel and entering the new value in the dialog that pops up:<img data-width="50%" data-align="left" data-featurebase-content-key="6800ec2dd19f0b30a535f964/post/681182d7c70f46ca5c290109/01968461-9b3b-7ecc-bed0-0bfadd07b748/b64u-aW1hZ2UucG5n.png" src="https://6800ec2dd19f0b30a535f964.featurebase-attachments.com/c/post/681182d7c70f46ca5c290109/01968461-9b3b-7ecc-bed0-0bfadd07b748/b64u-aW1hZ2UucG5n.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260910T220000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260910%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=07c8f01dfe8278b4ca52144cfd45a62cc1fe332b5e97bf326ea869a9532c683c" data-featurebase-content-filename="image.png">I admit that I have perhaps most often made use of this to keep the UI usable when coming back to a project with thousands of stories after months of inactivity, since with too many stories and too low a velocity the number of iterations brings Pivotal Tracker to its knees to the point that the initial load of a project hangs, and with the current “Display more” at the bottom of panels LiteTracker (in its current design) shouldn’t have quite the same performance issues … but even so this feature is useful for the purpose of planning when changes might alter velocity.

Velocity Override Simulator

Currently, LiteTracker is missing the ability to set the Team strength for iterations. Sending the screenshot from PT how it looks like. <img data-width="100%" data-align="left" data-featurebase-content-key="6800ec2dd19f0b30a535f964/post/681e1333956a144f7637f9e8/0196b578-451f-72d0-8b15-6a73f580da2a/b64u-U2NyZWVuc2hvdCAyMDI1LTA1LTA5IGF0IDE2LjMzLjQzLnBuZw.png" data-featurebase-content-filename="Screenshot 2025-05-09 at 16.33.43.png" src="https://6800ec2dd19f0b30a535f964.featurebase-attachments.com/c/post/681e1333956a144f7637f9e8/0196b578-451f-72d0-8b15-6a73f580da2a/b64u-U2NyZWVuc2hvdCAyMDI1LTA1LTA5IGF0IDE2LjMzLjQzLnBuZw.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260910T220000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260910%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=910d4afd4faf0e561f57a106cf115dca6f5ffd6d1a767b7ae382eea0e033a9eb"><img data-width="100%" data-align="left" data-featurebase-content-key="6800ec2dd19f0b30a535f964/post/681e1333956a144f7637f9e8/0196b578-355c-7aad-8170-4678b6fabfe4/b64u-U2NyZWVuc2hvdCAyMDI1LTA1LTA5IGF0IDE2LjMzLjQ4LnBuZw.png" data-featurebase-content-filename="Screenshot 2025-05-09 at 16.33.48.png" src="https://6800ec2dd19f0b30a535f964.featurebase-attachments.com/c/post/681e1333956a144f7637f9e8/0196b578-355c-7aad-8170-4678b6fabfe4/b64u-U2NyZWVuc2hvdCAyMDI1LTA1LTA5IGF0IDE2LjMzLjQ4LnBuZw.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260910T220000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260910%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=7afcc3479ac1d11d4573b0a3508987c6685ab9c744ec04722617e58b2d785abc"> Also sending the link for the help center: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://www.pivotaltracker.com/help/articles/understanding_velocity/">https://www.pivotaltracker.com/help/articles/understanding_velocity/</a>

Ability to set Team Strength for iterations

Michal Říha

In the original PT you used to be able to drag a story from the backlog onto any open epic window and it would add the label for that epic. This made it easy to collect many backlog items into an epic without having to manually add the label to each one through the “open”, add label action.

Drag stories to epic to add the epic label

Robert Bousquet

As seen on story #87830Attachment link is a 404 - No webpage was found for the web address: https://eu.litetracker.com/rails/active_storage/blobs/redirect/…This has happened repeatedly within our project over multiple stories.

File attachment in comment links to 404

vernon@nitidbit.com

Is there an option to just get billed without card or google. I want to pay via my company but I do not have a creditcard or google/apple pay. Annual payment via invoice would work e.g.

Different way to pay for subscription

info@updraftcoaching.nl

Related to this request: https://litetracker.featurebase.app/p/email-updates-clearer-action-and-story-titleNow 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.

Emails from same story should thread/group together

Winston

Now that we have Slack Notifications, I’d really like to see the email notifications also support slack. It's important for two reasons:<ol><li>many of our team members rarely look at email but are always looking at Slack.</li><li>The current Slack integration shows all messages in one channel. But with a big team, that's a lot of messages going by, with only a few that are relevant to any particular person. With this feature, I could ignore the Slack channel with all the notifications, and recieve only the ones for my stories or where I am mentioned, as direct-messages.</li></ol>Currently here are the email notification categories found in https://eu.litetracker.com/notification_settings<ul><li>New stories/epcis</li><li>ownership change</li><li>story state</li><li>comments</li><li>commits</li><li>blockers</li><li>tasks</li><li>reviews</li></ul>Each of these sends an email under certain conditions. We could keep these settings as-is. But add one pulldown/input there to indicate if I want my notifications to be send to me (1) via email, (2) via Slack, (3) both

Slack as an option for existing email notifications.

Can you work with Drata to replace the Pivotal Tracker integration with Lite Tracker?

Anil Nair

Planned

Combine Current and Backlog

litetracker

It doesn’t appear I can reorder stories within an epic.

Reordering stories within an epic

Jennifer Masamitsu

In the original PT, there was a crosshairs icon on stories when you looked at them in other contexts than the backlog that linked directly to them in the backlog so you could easily find and move them. This was essential to sorting activities.

Target/Crosshairs icon that links to the story in the backlog (or icebox)

When the user finds a story either using a search or in an epic, and then changes the story’s state (or takes some other action that would cause the story either to not appear in that result-set or to change order once the search is re-run, other than maybe dragging it with the mouse), the story should still be visible in its same position in the search/epic panel, and should remain open until the user explicitly closes it.In LiteTracker currently, if I find a story in the “Icebox stories” section of an epic and use the state dropdown field to change its state to “accepted”, it jumps up to the top (“Done stories” if it had a label) section.

Order in search/epic panel should be preserved

I previously requested <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://litetracker.featurebase.app/p/developer-api">a developer API</a>; the other side of the coin is some way for code in another system to be notified of a user’s actions in your system without constantly polling. The way Pivotal Tracker did this is with <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://en.wikipedia.org/wiki/Webhook">webhooks</a>, which I am led to believe is the standard tool for this in the modern Web. It allowed the user to, in each project, register a URL that would be, any time a user took any action in the project, called with a POST request containing a JSON object describing the action. (I think Pivotal Tracker only allowed one webhook per project, rather than as many as the user needed …) For a long time I used this (via Integromat, now Make.com) to add new stories to a Google Sheet, which I used for cross-project planning (for reasons I won’t go into here); I only stopped doing that when a glitch somewhere in the pipeline led to my hitting the Integromat free tier usage limit for the month.It would be nice to be able to select in the LiteTracker what kinds of activity to receive notifications about via the (or a) webhook; for my use case I only cared about newly created stories (though with filtering I might have added something for deletion or state transitions), and the flood of calls that caused me to stop using it was almost entirely “story X moved to after story Y”. But that’s secondary to having (reliable) webhooks in the first place.

Webhooks notifications

First of all, thank you for participating in this roadmap. It will help improve LiteTracker. We would ask people 2 things:<ul><li>Please search through posts if there is something you want to post already exists, or exists in very similar form. And comment on that post rather then adding new one. </li><li>When submitting post, ideally, we would like to have description, some use case and ideally an image or a video of what you would like to be implemented. Since 30. April is around the corner, it would be even better if posts can be submitted proactively, not only when you encounter an issue, as documenting everything will be much harder after 30. April. </li></ul>Thank you.

High Priority

!Important! For users of this board.

I really like the new Slack integration—it lets me see LiteTracker activity in the place where I’m already looking.However, I find the format of the messages too verbose. I know what the stories are about since that’s my day-to-day work. I’d like just a very short update. My wish would be for the messages to look like this instead. It mimics the subject lines used in email updates:[ $PROJECT ] $WHO $DESCRIPTION $LINK_TO_STORYe.g.[MyProject] Winston Wolff commented: This is my comment [#86237 - testing slack integration](URL to story in LiteTracker)[MyProject]The differences with the current output are:<ul><li>Adds the project name: [MyProject]</li><li>Removes details like Type, State, and Points. I don’t want that in Slack—it takes up too much space. If I need those details, I can click on the link and see it immediately.</li></ul><img data-width="100%" data-align="left" alt="" data-featurebase-content-key="6800ec2dd19f0b30a535f964/post/69a60219d1498a87990c311f/019cb06e-c7ad-7472-9598-1b28372c93ae/b64u-U2NyZWVuc2hvdCAyMDI2LTAzLTAyIGF0IDExLjU1LjExLnBuZw.png" src="https://6800ec2dd19f0b30a535f964.featurebase-attachments.com/c/post/69a60219d1498a87990c311f/019cb06e-c7ad-7472-9598-1b28372c93ae/b64u-U2NyZWVuc2hvdCAyMDI2LTAzLTAyIGF0IDExLjU1LjExLnBuZw.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260910T220000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260910%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=dbf063191172c734b0a9f358fdfd4b44f00194d6f49036af4cca6e3798271628" data-featurebase-content-filename="Screenshot 2026-03-02 at 11.55.11.png">

More succinct Slack messages

If I’m filtered by a user, and I remove that user as an owner, the story immediately disappears from the view (even before I have time to assign it to someone else). Pivotal Tracker kept it there until you refreshed. Can we mimic the PT behavior? I know it seems minor, but this happens every day as we reassign stories constantly, and it’s disruptive that the story just disappears from view.

When I remove an owner from a story, it just disappears from the column

Ethan Anderson

<a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://litetracker.com/integrations/github">API documentation </a> recommends downloading Luminous for Github integration, but "Luminous" is used by multiple organizations for different products, and the specific integration platform for LiteTracker isn't clearly identified.

API documentation vague

Alison Cordeiro

I am missing the ability to move multiple selected stories all together within the same project, e.g. to reorder roadmap or to move multiple tickets from icebox to backlog.

Move multiple selected stories

Carsten Mohs

Workspaces

One of the features of Pivotal Tracker that I made the most use of over the years is its API: I created shell scripts to add stories more quickly and reliably than I could using the UI, I set up connections in services like ITTT and Integromat (now Make) that didn’t officially support Tracker to create stories when certain conditions occurred, and once I created a shell script to rearrange hundreds of stories in a project’s backlog into a new order. Officially-supported “integrations” with other services can be quite useful, but an API is in my opinion better and more important.

Developer API

<ul><li>Auto Scroll when moving a story down or up (Deal breaker for us)</li><li>Batch move stories from Ice to BLog (Influences our decision)</li><li>Hitting Enter should save the story (Nice to have)</li></ul>

Auto Scroll + Batch Move + Hitting Enter after editing story

Jay Maxwell

In Pivotal Tracker, panels have three-dots menu with a variety of items. Whether each item is worth implementing and including should be decided individually, but since PT’s closure is imminent I thought it best to document what the options are.<ul><li>In the “Done” panel:<ul><li>“Select all”</li><li>“Deselect all” if any are selected</li><li>“Clone panel”</li><li>“Expand all iterations”</li><li>“Collapse all iterations”</li><li>Either “Hide empty iterations” or “Show empty iterations”</li></ul></li><li>In the combined “Current Iteration” and backlog panel:<ul><li>“Select all”</li><li>“Deselect all” if any are selected"</li><li>“Clone panel”</li><li>“Expand all iterations”</li><li>“Collapse all iterations”</li><li>“Hide empty iterations” or “Show empty iterations”</li><li>“Split Current Iteration and Backlog”</li><li>“Add stories to bottom of panel” or “Add stories to top of panel”</li></ul></li><li>In the split “Current Iteration” panel:<ul><li>“Select all”</li><li>“Deselect all” if applicable</li><li>“Clone Panel”</li><li>“Combine Current Iteration and Backlog”</li></ul></li><li>In the split “Backlog” panel:<ul><li>“Select all”</li><li>“Deselect all” if applicable</li><li>“Clone panel”</li><li>“Expand all iterations”</li><li>“Collapse all iterations”</li><li>“Hide empty iterations” or “Show empty iterations”</li><li>“Combine Current Iteration and Backlog”</li><li>“Add stories to bottom of panel” or “Add stories to top of panel”</li></ul></li><li>In the Icebox:<ul><li>“Select all”</li><li>“Deselect all” if applicable</li><li>“Clone panel”</li><li>“Expand all release markers” (relating to the relatively-recent feature allowing organization of the Icebox using “release” stories as basically collapsible folders)</li><li>“Collapse all release markers”</li><li>“Add stories to bottom of panel” or “Add stories to top of panel”</li></ul></li><li>Within an epic:<ul><li>“Select all”</li><li>“Deselect all” if applicable</li></ul></li><li>Within a saved search panel:<ul><li>“Select all”</li><li>“Deselect all” if applicable</li><li>“Share search” (I’m not sure how this feature worked)</li><li>“Edit saved search”</li><li>“Delete saved search”</li><li>“Enable auto-refresh” or “Disable auto-refresh” (“auto-refresh” would rerun the search every so often to reflect changes to stories).</li></ul></li><li>Within a non-saved search:<ul><li>“Select all”</li><li>“Deselect all” if applicable</li><li>“Share search”</li><li>“Pin search” (which prevents the panel from closing if the user does another search, which would usually put its results into the same panel)</li><li>“Save search to sidebar”</li><li>“Enable auto-refresh” or “Disable auto-refresh”.</li></ul></li></ul>(I think that in any of these “Select all” may not have been available if there were no stories at all.)

More Panel Options

I have a story in the backlog and I wish to reorder it backwards a number of sprints.After reloading the page, the story is back in its initial position.Even moving the story to the icebox and then back to the backlog in a new position does not retain the same order.

Completed

Re-Ordering story in backlog is not permanent

Michael Amygdalidis

Paste attachments from the system clipboard directly into a comment like in the PivotalTracker would be very convenient.

Paste of attachments into comments

Thomas Zuhl

The clone story functionality isn’t working and it is crutial for our worflow because we have template stories that we clone<img data-width="100%" data-align="left" data-featurebase-content-key="6800ec2dd19f0b30a535f964/post/6806c2ec54740e30c3897a09/01965a69-64f0-7fd8-a333-03cb91f006ed/b64u-U2NyZWVuc2hvdCAyMDI1LTA0LTIxIGF0IDE2LjEyLjMyLnBuZw.png" data-featurebase-content-filename="Screenshot 2025-04-21 at 16.12.32.png" src="https://6800ec2dd19f0b30a535f964.featurebase-attachments.com/c/post/6806c2ec54740e30c3897a09/01965a69-64f0-7fd8-a333-03cb91f006ed/b64u-U2NyZWVuc2hvdCAyMDI1LTA0LTIxIGF0IDE2LjEyLjMyLnBuZw.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260910T220000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260910%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=a075c43725071c06fad0b85635a9750c027e9158d867e8bbe9725c2aa204075f">

Clone story button is disable

Alexis Gonzalez

Email Notifications

Bugs and chores shouldn't have estimates

Please make it work on the iPhone.

Need iPhone Version

Peter Redford

Currently, LiteTracker is missing the history (changelog) for each story. Right now, the button is disabled, and we would like to get this feature added. <img data-width="100%" data-align="left" data-featurebase-content-key="6800ec2dd19f0b30a535f964/post/681e0ba9fd616563a977a50b/0196b55a-ec44-734f-bc0a-9aa0d977dfb3/b64u-U2NyZWVuc2hvdCAyMDI1LTA1LTA5IGF0IDE2LjAyLjI4LnBuZw.png" data-featurebase-content-filename="Screenshot 2025-05-09 at 16.02.28.png" src="https://6800ec2dd19f0b30a535f964.featurebase-attachments.com/c/post/681e0ba9fd616563a977a50b/0196b55a-ec44-734f-bc0a-9aa0d977dfb3/b64u-U2NyZWVuc2hvdCAyMDI1LTA1LTA5IGF0IDE2LjAyLjI4LnBuZw.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260910T220000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260910%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=cec5ccbf4817dddd2145c230378c84f390b2d5337cc451d0a78646d8debb5a55"> Also, I want to be able to see history for already imported stories.

Story History

Updates to the LiteTracker stories are not showing up for other users in real-time as they do on Pivotal Tracker.Example: Person A is on story X. Person B makes an update on story X (comment, change status etc). Person A is not able to see that change unless they refresh the story.In Pivotal Tracker, a refresh was not required for the update to be seen.

Story updates are not in real-time

Pearlin Yang

In Pivotal Tracker, I could just paste a screenshot in from the clipboard directly into the comments.In Lite Tracker, I have to create the story and click save because it doesn’t expose the comments field on new stories. Then I have to go back into the story and attach a file because it doesn’t allow me to paste screenshots from the clipboard into the comments. This is making it really painful to attach screenshots to new stories.

Very hard to attach screenshots to a new story

Today (30 apr), I wrote a story and immediately after clicking save, it has disappeared. If it helps to track down the bug, here’s my project:<a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://eu.litetracker.com/n/projects/fd1675">https://eu.litetracker.com/n/projects/fd1675</a>I don’t have a screenshot, but the title was something like: “lets organize the methods for models/clinic.rb”Clearly, this is a very serious bug—if our data randomly disappears, then LiteTracker is useless.