View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0021072 | mantisbt | timeline | public | 2016-06-09 05:58 | 2016-08-28 01:12 |
Reporter | cproensa | Assigned To | cproensa | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Product Version | 1.3.0-rc.1 | ||||
Target Version | 1.3.1 | Fixed in Version | 1.3.1 | ||
Summary | 0021072: Timeline only show issues from current project | ||||
Description | This may be as designed, but there's an inconsistency with the scope showed in timeline, from that showed by filters in my view page. "my view" filters show issues in current project, and all subprojects. However, when current project is "all projects", Timeline shows history items for all projects and subprojects to any depth. Imho, Timeline behaviour should match that of "my view". | ||||
Tags | No tags attached. | ||||
I agree |
|
Project scope for the timeline should then be quite like the filter visibility is calculated, regarding project and subprojects. For a better solution, instead of adding new logic to get the right project selection, i could add a history selection to be based on a filter. The new filter based history_get_range_result can be used to build timelines or history listing for any need:
|
|
i've got a patch ready, but as said, it is based on commits of previous PR. |
|
MantisBT: master-1.3.x 28b6d799 2016-08-05 01:21 Committer: dregad Details Diff |
Make timeline show a set of bugs based on filters Make timeline show history for a set of bugs based on a filter. By default, create a filter to show current project and subprojects, to match the visibility of my view page. Fixes: 0021072 Signed-off-by: Damien Regad <dregad@mantisbt.org> Original commit modified to remove unnecessary assignment. |
Affected Issues 0021072 |
|
mod - core/timeline_api.php | Diff File | ||
MantisBT: master-1.3.x e48e7375 2016-08-05 01:26 Committer: dregad Details Diff |
Revert limit history range to current project Revert the changes made by Issue 0019945 (commit adbd0882). The api function history_get_event_from_row should not impose a limitation for current project queries. The original timeline issue, which 0019945 was addressing, has now been resolved in another way, see issue 0021072. Fixes: 0021146 |
Affected Issues 0019945, 0021072, 0021146 |
|
mod - core/history_api.php | Diff File | ||
MantisBT: master-1.3.x 4d160125 2016-08-19 17:02 Committer: dregad Details Diff |
Fix querying zero projects Fix the new api functions, to support the case when a user doesn't have any accessible project. In this case the filter query can't be built, so fix returning empty values. Affected functions were introduced in relation to Issues 0020424, 0021072. |
Affected Issues 0020424, 0021072 |
|
mod - core/database_api.php | Diff File | ||
mod - core/filter_api.php | Diff File | ||
mod - core/history_api.php | Diff File |