User-centric storage. Last-viewed information and 'intelligent' followup
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.
Change History
(15)
| Summary: |
Store last-viewed information about cookies → Store last-viewed information and 'intelligent' followup
|
| Milestone: |
→ 0.8
|
| Priority: |
normal → highest
|
| Summary: |
Store last-viewed information and 'intelligent' followup → User-centric storage. Last-viewed information and 'intelligent' followup
|
| Owner: |
changed from Jonas Borgström to anonymous
|
| Status: |
new → assigned
|
| Owner: |
changed from anonymous to Jonas Borgström
|
| Owner: |
changed from Jonas Borgström to daniel
|
| Keywords: |
project added
|
| Milestone: |
→ 1.0
|
| Priority: |
highest → normal
|
| Severity: |
normal → major
|
| Keywords: |
user tracobject added; project removed
|
| Milestone: |
1.0 → 0.12
|
| Owner: |
daniel removed
|
| Status: |
assigned → new
|
| Owner: |
set to anonymous
|
| Status: |
new → assigned
|
| Owner: |
anonymous removed
|
| Status: |
assigned → new
|
| Cc: |
a.a.vykhodtsev@… added
|
| Milestone: |
next-major-0.1X → unscheduled
|
This is not my ticket :)