1. Bitbucket
  2. Public Issue Tracker
  3. master
  4. Issues

Issues

Issue #2872 duplicate

Persistent filter/sort for issue tracker

Jon Langevin
created an issue

It would be quite nice if we could save issue filtering and sorting. Ideally we would be able to save presets on the project level and at the user level, and additionally designate the default filter to use on both project and user level.

Comments (4)

  1. David Chambers

    Do you imagine that persistence would be achieved implicitly (via a cookie) or explicitly (via a setting)?

    One approach would be to save the last query in a repo-specific cookie, and perform this filter each time the list of issues is viewed. Updating the query would update the cookie. Anything more involved than this sounds like quite a bit of work, and we don't have much time to devote to the issue tracker at this stage.

    In the interim, bookmarking filtered issues lists may be helpful.

  2. Jon Langevin reporter

    Ideally, both. If anything, cookie persistence could be stage 1 just to get the functionality in, then add explicit persistence later on when you guys have time.

    Additionally, as a when-you-have-time feature, it would be nice to have the ability to go to previous & next ticket, when inside a ticket view, using the cookie/session-applied filter. If no filter is applied, then the default display/sort should ideally be considered a filter, so that previous/next still functions as expected.

    Some or all of this exists in how Assembla allows ticket navigation. I think their implementation is much more than needed here, as simple filter persistence and ticket filter navigation would be *very* handy.

    Any stopgap solution until you guys can devote more time, would be quite appreciated.

  3. Log in to comment