Ticket #150 (new enhancement)
User-centric storage. Last-viewed information and 'intelligent' followup
| Reported by: | daniel | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.12 |
| Component: | general | Version: | devel |
| Severity: | major | Keywords: | user tracobject |
| Cc: |
Description
This ties in to a more advanced form of "user" centric development, including personalized settings (#63, #17, #1) and such stuff.
An idea for storing and using 'user trails'
We could generate a random "id" key, store it in a cookie, and use it for logging what the user has viewed throughout the system.
Using this information, we could do the following neat things:
- The timeline could highlight events changed since last viewed.
- List tickets previously viewed, but changed (aka 'interesting' tickets). All automatically, without need for any "watch this" features.
This is how Archive stores a users' read list posts, and it's quite clever.
Attachments
Change History
Note: See
TracTickets for help on using
tickets.
