Ticket #843 (closed defect: duplicate)
Opened 7 years ago
Last modified 6 years ago
Filter timeline by user ID
| Reported by: | pkou@… | Owned by: | jonas |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | timeline | Version: | 0.7.1 |
| Severity: | normal | Keywords: | |
| Cc: | pkou@… | ||
| Release Notes: | |||
| API Changes: | |||
Description
Add possibility to filter timeline by user ID or user mask.
The filter for timeline will look like:
- View changes from [date] and [days] days back
- [x] Ticket changes
- [x] Repository checkins
- [x] Wiki changes
- [x] Milestones
- [x] Changes by user [usermask]
The usermask specifies user for which changes are displayed.
Attachments
Change History
comment:1 Changed 7 years ago by jonner
comment:2 Changed 7 years ago by pkou@…
- Cc pkou@… added
Agree. The location of the new field can be changed. Initially, I was going to suggest modification of first line, e.g.
View changes from [date] and [days] days back for user [user]
But it does not look good because overal length of filter box will be increased and because the UI will be not logical by default, when user is empty.
As an option, the new field can be added on the right of existing check boxes (as a second column, with right alignment). It will look like the following:
View changes from [MM/DD/YY ] and [NN ] days back [x] Ticket changes | Changes by user [usermask ] [x] Repository checkins | [x] Wiki changes | [x] Milestones | Update
The field usermask is ignored when it is empty.
Changed 7 years ago by pkou@…
- Attachment patch-changesbyuser-r1011.diff added
Patch for the changes
Changed 7 years ago by pkou@…
- Attachment patch-changesbyuser-r1011-v2.diff added
A much more elegant patch for the issue
comment:3 Changed 7 years ago by pkou <pkou at ua.fm>
Please review attached patch (v2).
comment:4 Changed 6 years ago by anonymous
New patch attached in #1198
comment:5 Changed 6 years ago by cboos
- Resolution set to duplicate
- Status changed from new to closed
Closed as a duplicate of #1198.



I kind of like the idea, but the proposed user interface doesn't seem quite right. The current 4 checkboxes are all particular types of items that you can choose to display or not. The fifth is something completely different.