# Feature SPPM-221 - Comment fields for project attributes

Project: Stream Project Portfolio Management
Status: closed
URL: https://community.openproject.org/work_packages/SPPM-221

## Planning

| Attribute | Value |
| --- | --- |
| Date | 2026-02-04 – 2026-03-05 |
| Priority | Medium |
| Target versions | 17.2.0 |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| SPPM-296 | Bug | Comment field not included in PDF export of PIR | closed |  | 17.2.0 |  | Modules and project features / Project attributes, Modules and project features / Project lifecyle - phases and gates |
| SPPM-295 | Task | Comment fields for project attributes leftovers | closed | Ivan Kuchin | 17.2.0 |  |  |
| SPPM-290 | Code maintenance | Refactoring while adding custom field comments | closed |  | 17.2.0 |  |  |
| SPPM-297 | Bug | Project attribute comment not visible in pdf export for non-admins | rejected |  | 17.2.0 |  | Modules and project features / Project attributes, Modules and project features / Export / PDF Export |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Project attributes |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups | https://www.figma.com/design/Ya9Xz4HvWCzOmM64qfvGPm/Projects-attributes?node-id=2364-66789 |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers | OP Dev Polaris Team |
| Designer | Marc Alcobé |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As a** project portfolio manager  
**I want to** have a comment field for project attributes  
**so that I** better understand why a specific values has been chosen.

**Acceptance criteria:**

- [x] In the tab `Details` while creating or editing a project attribute, a new checkbox is available:
  
    - **Add a comment text field:** Allows the user to add a comment related to the project attribute when selecting the value in the project overview.

- [x] Once the checkbox is selected, when the user access the project attribute through the `Project Overview` a modal with the value to fill or edit will open and below it a text area will be available for the users to add comments.

- [x] In the `Project Overview` page, all project attributes are now editable individually, not by section.
  
    - ~~Those values that can be edited inline (e.g. short text, integer, float, list…) will be editable inline.~~
  
    - ~~Those values that have comments or can't be edited inline will be edited in a modal (e.g. long text).~~
  
    - The comment field is added to the modal which opens when the user clicks to edit the field and is saved along with the value.

- [x] ~~The comment field is only shown for:~~ The comment field is shown for all field types.
  
  - [x] ~~Boolean~~
  - [x] ~~Date~~
  - [x] ~~Float~~
  - [x] ~~Int~~
  - [ ] ~~Link~~
  - [x] ~~List~~
  - [ ] ~~Text~~
  - [ ] ~~Long text~~
  - [x] ~~User~~
  - [x] ~~Version~~
  - [x] ~~Calculated value~~

- [x] Users that can edit a project attribute can also edit the comment.

- [x] Users that can view a project attribute can also view the comment. The attribute modal should open, but in a read-only mode.

- [x] Changes to the comments are shown in the project activity
  
    - This follows the same pattern as the project description column. A “Details” link is displayed, and the user can follow it to see a diff.
  
    - If the comment functionality is disabled later on, when comments already exist, they are not displayed. Once the comment is reactivated on the field, all comments are shown again.

- [x] Comments can be selected as separate columns in the project list.
  
    - The column is named "X comment" where X is the name of the custom field the comment is configured for.
  
    - The text might be abbreviated. This follows the same pattern as the project description column. In case the text is abbreviated, a link to open a modal is displayed.

- [x] Comments can be exported (.csv, .xlsx, .pdf)

- [x] The comment field is a simple multi-row text field without text formatting, macros, tables, pictures etc. (we might change this to a “normal text field” later).

- [x] The comments are displayed in the API and can also be updated using it.

- [x] The comment field is displayed along with the field it is activated on in a PIR.
  
  - [ ] The comment field is included in the PDF print out of the PIR 

**Permissions:**

  - Administration of project attributes is limited to admins (same as before)

  - Adding/Changing a comment on a project attribute requires the same permission as adding/changing the value of the associated project attribute.

  - Viewing a comment on a project attribute requires the same permission as viewing the value of the associated project attribute.

**Technical notes:**

  - 
    <br>

**Out of scope:**

  - Attribute help texts fixed by the administrator are going to be reworked on this work package: <mention class="mention" data-id="65413" data-type="work_package" data-text="###65413">\#\#\#65413</mention>

  - Filtering and ordering on the comment in the project list