Content
View differences
Updated by Oliver Günther almost 11 years ago
**As** an OpenProject user
**I want** repository revisions belonging to a work package to be displayed in the work package show view
**so that** I can quickly see which revisions belong to a work package.
**Acceptance criteria**
- The revisions are shown within the existing activity tab. There is <ins>no</ins> separate tab only for revisions.
- If there is a commit in the repository module referencing the work package the changeset is shown in the activity list.
- Only users with the permissions to see commits can see the reference.
- The displayed revisions are ordered reverse-chronological
- The revisions in the activity tab includes the:
- name of the associated commit (“Revision \[Revision-ID\]”, whereas \[Revision-ID\] is the revision ID associated to the commit) as a link to the commit in the repository
- username of the user performing the commit as a link to the personal profile
- the username follows the format chosen in the admin settings (Administration \> Settings \> Display tab \> User display format)
- time when the commit was made (as a link to the project activity), the time is displayed in the known format (e.g. “11 months ago”)
- the commit message provided when making the commit with a link of the referenced (work package(s))
- OpenProject installations in subfolders are fully supported
**Technical solution concept**
- Separate API v3 endpoints
- `api/v3/work_packages/:id/journals` - exists (also it is named activities right now)
- `api/v3/work_packages/:id/revisions` - to be created (\#19342)
- Aggregation of journals and revisions happens in the front-end (\#21047)
- Interlacing
**Out of scope**
- Filter the activities for revisions, comments, status changes etc.
- Distinct end point for all activities around the work package
- Journals
- Revisions
- Mentions in wikis
- Mentions in other work packages
- …
- Pagination in the backend. If performance becomes an issue, we have to review this.
**I want** repository revisions belonging to a work package to be displayed in the work package show view
**so that** I can quickly see which revisions belong to a work package.
**Acceptance criteria**
- The revisions are shown within the existing activity tab. There is <ins>no</ins> separate tab only for revisions.
- If there is a commit in the repository module referencing the work package the changeset is shown in the activity list.
- Only users with the permissions to see commits can see the reference.
- The displayed revisions are ordered reverse-chronological
- The revisions in the activity tab includes the:
- name of the associated commit (“Revision \[Revision-ID\]”, whereas \[Revision-ID\] is the revision ID associated to the commit) as a link to the commit in the repository
- username of the user performing the commit as a link to the personal profile
- the username follows the format chosen in the admin settings (Administration \> Settings \> Display tab \> User display format)
-
-
- OpenProject installations in subfolders are fully supported
**Technical solution concept**
- Separate API v3 endpoints
- `api/v3/work_packages/:id/journals` - exists (also it is named activities right now)
- `api/v3/work_packages/:id/revisions` - to be created (\#19342)
- Aggregation of journals and revisions happens in the front-end (\#21047)
- Interlacing
**Out of scope**
- Filter the activities for revisions, comments, status changes etc.
- Distinct end point for all activities around the work package
- Journals
- Revisions
- Mentions in wikis
- Mentions in other work packages
- …
- Pagination in the backend. If performance becomes an issue, we have to review this.