# Feature COMMS-155 - Consistent visualizations of the creation date of work packages

Project: Stream Communicator
Status: in specification
URL: https://community.openproject.org/work_packages/COMMS-155

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Low |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket | Features (random) |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Parimal Satyal |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** a reader of a work package  
**I want to** have a clear communication of the creation date the work package that is consistent in all work packages  
**so that** I don't need to search for it

**Acceptance criteria**

  - The creation date looks the same and is at the same position for all work packages, independent of the fact if a comment got aggregated into the same journal entry
    
      - One location: The small info line below the subject not only show the creator's name but also the date when a work package was created. Followed by the information when it was last updated
    
      - Another location: In the **Activity** tab the creation event is listed independently of any other following change or comment to the work package.
        
          - For backward compatibility with elder work packages one aspect needs to be respected: Sometimes the first comment on a work package gets aggregated into one journal entry on the database level. A new visual representation should not introduce a new journal version in the frontend as otherwise old links would not point to the same journal entry anymore.

**Visuals**

**Creation date on info line**

<figure class="image image_resized op-uc-figure" style="width:543px;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/240395/content"></div></figure>

**Separate creation event for all work packages** (using existing design; we'll have to figure out the numbering. For example, using <mention class="mention" data-id="1" data-type="work_package" data-text="#1">#1</mention> for both, or not include a number for the creation event).

<img class="image_resized op-uc-image op-uc-image_inline" style="width:934px;" src="/api/v3/attachments/257111/content">