Content
View differences
Updated by Rince wind over 3 years ago
Updating the user activity page to use the same angular components as the new project (/work package) activity module as described in ##43852. ##43852.
**Status Quo**
<img class="op-uc-image op-uc-image_inline" style="width:1367px;" src="/api/v3/attachments/42646/content">
**Expected design update similar to**
**<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/42647/content">**
**Acceptance criteria**
* This task is only about updating the view to be inline with other newest changes.
* The goal is to recycle the angular component and other front end modules at the top most level possible to
* Achieve a nicely designed full screen view (not only half the page as it is now)
* Get the information what fields changed in the record aside from the new comment
* Automatically allow paging through the view
* Include changes of project attributes
* Changes required in addition to the new project activity codebase
* [ ] Allow to filter for the actor of the new record
* [ ] Disengage the project filter of the query (filter for all changes made in any project)
* [ ] Allow the activity component (by a simple boolean var; no need to automatically calculate that) to hide the "updated by **{user}**" below the entry title and set it to **true** while embedding in the user activity page.
* [ ] Minor redesign of the current user activity view (e.g. placing the "Reported work packages" below the user name and then place the activity component with the altered search query.
**Out of Scope**
* Support for altering the filter by the user. The project activity view includes filter options in the sidebar. Since the sidebar is not present in the user activity view, don't implement that. The filter can be predefined and hard coded to include any subset of "Budgets, News, Spent time, Wiki edits, Work packages, Project attributes". Since the new angular component from ##43852 is doing all the rendering, no additional work is required for any of these change entries to be available.
**Advantages**
* Decreasing the codebase in size. Always a good trait. Less code » less possibilities for bugs » less stuff to maintain.
* Updating the project activity module directly benefits a larger part of the application. E.g. implementing ##44986 #[#44986](https://community.openproject.org/work_packages/44986) will benefit a wider user range or getting the pagination functionality that is currently missing. range.
* Stream lining the application by clean up tasks like this one makes the application look more polished.
**Status Quo**
<img class="op-uc-image op-uc-image_inline" style="width:1367px;" src="/api/v3/attachments/42646/content">
**<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/42647/content">**
* This task is only about updating the view to be inline with other newest changes.
* The goal is to recycle the angular component and other front end modules at the top most level possible to
* Achieve a nicely designed full screen view (not only half the page as it is now)
* Get the information what fields changed in the record aside from the new comment
* Automatically allow paging through the view
* Include changes of project attributes
* Changes required in addition to the new project activity codebase
* [ ] Allow to filter for the actor of the new record
* [ ] Disengage the project filter of the query (filter for all changes made in any project)
* [ ] Allow the activity component (by a simple boolean var; no need to automatically calculate that) to hide the "updated by **{user}**" below the entry title and set it to **true** while embedding in the user activity page.
* [ ] Minor redesign of the current user activity view (e.g. placing the "Reported work packages" below the user name and then place the activity component with the altered search query.
**Out of Scope**
* Support for altering the filter by the user. The project activity view includes filter options in the sidebar. Since the sidebar is not present in the user activity view, don't implement that. The filter can be predefined and hard coded to include any subset of "Budgets, News, Spent time, Wiki edits, Work packages, Project attributes". Since the new angular component from ##43852 is doing all the rendering, no additional work is required for any of these change entries to be available.
**Advantages**
* Decreasing the codebase in size. Always a good trait. Less code » less possibilities for bugs » less stuff to maintain.
* Updating the project activity module directly benefits a larger part of the application. E.g. implementing ##44986
* Stream lining the application by clean up tasks like this one makes the application look more polished.