04/11/2025

• Open Point STC-300: How to handle exposing internal comments on the API?
  updated by Kabiru Mwenja on 04/11/2025 12:47 PM
  • Comment added

    Bruno Pagno shall we set the decision to Option (1) as per dev open door?

• Implementation STC-304: On edit set attachment replacements
  created by Kabiru Mwenja on 04/11/2025 12:28 PM
• Implementation STC-303: Adjust atom export to respect comment visibility
  updated by GitHub ⁤ on 04/11/2025 12:23 PM
  • Comment added

• Implementation STC-276: Update "Learn more" link to point to correct documentation once updated
  updated by Parimal Satyal on 04/11/2025 11:38 AM
  • Assignee set to Maya Berdygylyjova
• Implementation STC-276: Update "Learn more" link to point to correct documentation once updated
  updated by Maya Berdygylyjova on 04/11/2025 11:24 AM
  • Comment added

    Kabiru Mwenja Bruno Pagno I am now done with 15.5 docs and can start working on 16.0 docs on Monday. I'll create the lin...

• Implementation STC-276: Update "Learn more" link to point to correct documentation once updated
  updated by Parimal Satyal on 04/11/2025 11:21 AM
  • Comment added

    H team, I'll bring this up with the docs team and we'll see how we can proceed.

• Implementation STC-276: Update "Learn more" link to point to correct documentation once updated
  updated by Bruno Pagno on 04/11/2025 10:57 AM
  • Comment added

    Kabiru Mwenja sounds like the correct approach to me. I don't know exactly which work package you mean, though, but I wo...

• Implementation STC-276: Update "Learn more" link to point to correct documentation once updated
  updated by Kabiru Mwenja on 04/11/2025 10:36 AM
  • The changes were retracted.
• Implementation STC-276: Update "Learn more" link to point to correct documentation once updated
  updated by Kabiru Mwenja on 04/11/2025 10:36 AM
  • Comment added

    I think we would need to align with the @DocsTeam (Corinna Günther Maya Berdygylyjova ) - when the docs are ready we rem...

• Bug STC-302: The auto time-tracking timer button keeps changing width when the timer is running
  updated by Parimal Satyal on 04/11/2025 10:32 AM
  • Assignee set to Alexander Coles
• Feature STC-299: Additional protections for internal comments in places where comments are accessed
  updated by Bruno Pagno on 04/11/2025 10:25 AM
  • Version set to 16.0.0
• Implementation STC-303: Adjust atom export to respect comment visibility
  created by Bruno Pagno on 04/11/2025 10:22 AM

04/10/2025

• Implementation STC-205: Ensure notifications work in both restricted and unrestricted state independent of permission changes
  updated by GitHub ⁤ on 04/10/2025 05:45 PM
  • Comment added

    opf/openproject#18451 deployed to qa.openproject-edge.com

• Implementation STC-205: Ensure notifications work in both restricted and unrestricted state independent of permission changes
  updated by Bruno Pagno on 04/10/2025 04:56 PM
  • Status changed from in development to closed
  • Assignee deleted (Bruno Pagno)
  • % Complete set to 100%
• Implementation STC-205: Ensure notifications work in both restricted and unrestricted state independent of permission changes
  updated by GitHub ⁤ on 04/10/2025 04:56 PM
  • Comment added

• Bug STC-302: The auto time-tracking timer button keeps changing width when the timer is running
  created by Parimal Satyal on 04/10/2025 03:53 PM
• Feature STC-230: Cosmetic UI optimisations to the emoji reactions
  updated by Ivan Kuchin on 04/10/2025 02:34 PM
  • Status changed from review failed to needs review
  • Assignee changed from Ivan Kuchin to Henriette Darge
• Implementation STC-205: Ensure notifications work in both restricted and unrestricted state independent of permission changes
  updated by GitHub ⁤ on 04/10/2025 12:04 PM
  • Comment added

• Feature STC-230: Cosmetic UI optimisations to the emoji reactions
  updated by Henriette Darge on 04/10/2025 08:14 AM
  • Status changed from in review to review failed
  • Assignee changed from Henriette Darge to Ivan Kuchin

04/09/2025

• Feature STC-230: Cosmetic UI optimisations to the emoji reactions
  updated by Henriette Darge on 04/09/2025 03:37 PM
  • Status changed from needs review to in review
  • Assignee changed from OP Dev Dream Team to Henriette Darge
• Open Point STC-300: How to handle exposing internal comments on the API?
  updated by Bruno Pagno on 04/09/2025 11:10 AM
  • Comment added

    Tokens are impersonating users
    The expectation when querying the data is that it would return the data the user can ...

• Bug STC-297: Exposing restricted comments when polling
  updated by Ivana Šugić on 04/09/2025 09:03 AM
  • Comment added

    Hi Bruno Pagno, thanks for the heads-up. Will keep it open and test it later then.

04/08/2025

• Feature STC-256: Group work package-related project settings in a new entry called 'Work packages'
  updated by Parimal Satyal on 04/08/2025 06:23 PM
  • Comment added

    Hi Corinna Günther,
    Indeed. This affects all users. It's just under the internal comments epic because the work was done...

• Bug STC-297: Exposing restricted comments when polling
  updated by GitHub ⁤ on 04/08/2025 06:15 PM
  • Comment added

    opf/openproject#18573 deployed to qa.openproject-edge.com

• Bug STC-297: Exposing restricted comments when polling
  updated by Bruno Pagno on 04/08/2025 05:47 PM
  • Comment added

    Ivana Šugić I created this bug mostly to keep track of things, but I'm not sure you want to validate this without having...

  • Status changed from review approved to merged
• Bug STC-297: Exposing restricted comments when polling
  updated by GitHub ⁤ on 04/08/2025 05:47 PM
  • Comment added

• Feature STC-299: Additional protections for internal comments in places where comments are accessed
  updated by Parimal Satyal on 04/08/2025 05:44 PM
  • Subject changed from Additional protections for restricted comments in places where comments are accessed to Additional protections for internal comments in places where comments are accessed
• Feature STC-209: Introduce Enterprise gate for internal comments in work packages
  updated by Parimal Satyal on 04/08/2025 05:44 PM
  • Subject changed from Introduce Enterprise gate for work package comments with restricted visibility to Introduce Enterprise gate for internal comments in work packages
  • Description changed (Details)
• Feature STC-295: Show warning if a user tries to uncheck the 'Internal comment' checkbox when there's already text in the comment box
  updated by Parimal Satyal on 04/08/2025 05:41 PM
  • Subject changed from Show warning if a user tries to 'unrestrict' a restricted-visibility comment when there's text in the comment box
    to Show warning if a user tries to uncheck the 'Internal comment' checkbox when there's already text in the comment box
  • Description changed (Details)
• Feature STC-219: Enterprise/Professional upsale banners for internal comments
  updated by Parimal Satyal on 04/08/2025 05:41 PM
  • Subject changed from Enterprise/Professional upsale banners for “Comments with restricted visibility” to Enterprise/Professional upsale banners for internal comments
• Feature STC-199: Introduce internal comments
  updated by Parimal Satyal on 04/08/2025 05:41 PM
  • Subject changed from Introduce work package comments with restricted visibility to Introduce internal comments
• Open Point STC-218: What plans will have the feature “internal comments”?
  updated by Parimal Satyal on 04/08/2025 05:40 PM
  • Subject changed from What plans will have the feature “comments with restricted visibility”? to What plans will have the feature “internal comments”?
• Open Point STC-213: What happens if you check the 'Internal comment' checkbox after after having mentioned somebody?
  updated by Parimal Satyal on 04/08/2025 05:39 PM
  • Subject changed from What happens if you check the 'Restricted visibility' checkbox after after having mentioned somebody?
    to What happens if you check the 'Internal comment' checkbox after after having mentioned somebody?
  • Decision changed from For 15.5: An @mention will turn into plain text if 'Restrict visibility' checked and the user in question doesn't have the necessary permissions. Unchecking it will not restore the @mention.
    to For 15.5: An @mention will turn into plain text if the 'Internal comment' checked and the user in question doesn't have the necessary permissions. Unchecking it will not restore the @mention.
• Open Point STC-212: Should someone be able to make a previously-posted internal comment public?
  updated by Parimal Satyal on 04/08/2025 05:38 PM
  • Subject changed from Can one un-restrict a comment that originally posted with restrictive visibility? to Should someone be able to make a previously-posted internal comment public?
  • Decision set to Once you post a comment, you cannot change its visibility. The edit screen simply doesn't have a control to change it. If you posted a public comment that was meant to be private or vice-versa, you need to delete it and post another comment.
• Open Point STC-211: How can internal comments be enabled/disabled at a project level?
  updated by Parimal Satyal on 04/08/2025 05:37 PM
  • Subject changed from How can comments with restrictive visibility be enabled/disabled at a project level? to How can internal comments be enabled/disabled at a project level?
  • Decision changed from Settings will be in a new tab called 'Activity' in the new consolidated 'Work packages' page in Project settings.
    to Settings will be in a new tab called 'Internal comments' in the new consolidated 'Work packages' page in Project settings.
• Open Point STC-194: How do we call confidential/helpdesk/restricted/internal comments?
  updated by Parimal Satyal on 04/08/2025 05:36 PM
  • Comment added

    After a discussion with the feature team and team leads, we have decided to update this decision to a new name: Internal...

  • Status changed from resolved to decided
  • % Complete set to 100%
  • Decision set to This feature will be called "Internal comments"
  • Involved people set to Wieland Lindenthal, Ivana Šugić, Kabiru Mwenja, Cécile Guiot, Bruno Pagno
• Epic STC-1: Internal comments in the work package activity tab
  updated by Parimal Satyal on 04/08/2025 05:34 PM
  • Comment added

    After our decision today to rename this feature "Internal comments", I've gone ahead and updated the epic (and related o...

  • Subject changed from Work package comments with restricted visibility to Internal comments in the work package activity tab
  • Motivation and background information changed (Details)
  • Acceptance criteria changed (Details)
• Bug STC-297: Exposing restricted comments when polling
  updated by Kabiru Mwenja on 04/08/2025 05:20 PM
  • Status changed from needs review to review approved
• Feature STC-219: Enterprise/Professional upsale banners for “Comments with restricted visibility”
  updated by GitHub ⁤ on 04/08/2025 02:15 PM
  • Comment added

    opf/openproject#18407 deployed to qa.openproject-edge.com

• Implementation STC-208: Add capability to enable and disable work package comment with restricted visibility at project level
  updated by GitHub ⁤ on 04/08/2025 02:15 PM
  • Comment added

    opf/openproject#18407 deployed to qa.openproject-edge.com

• Feature STC-230: Cosmetic UI optimisations to the emoji reactions
  updated by Ivan Kuchin on 04/08/2025 01:58 PM
  • Status changed from in specification to needs review
  • Assignee changed from Ivan Kuchin to OP Dev Dream Team
• Bug STC-297: Exposing restricted comments when polling
  updated by Bruno Pagno on 04/08/2025 01:36 PM
  • Subject changed from Leaking restricted comments when polling to Exposing restricted comments when polling
• Implementation STC-208: Add capability to enable and disable work package comment with restricted visibility at project level
  updated by Bruno Pagno on 04/08/2025 01:26 PM
  • Status changed from in review to closed
  • Assignee deleted (Kabiru Mwenja)
  • % Complete set to 100%
• Feature STC-219: Enterprise/Professional upsale banners for “Comments with restricted visibility”
  updated by GitHub ⁤ on 04/08/2025 01:26 PM
  • Comment added

• Implementation STC-208: Add capability to enable and disable work package comment with restricted visibility at project level
  updated by GitHub ⁤ on 04/08/2025 01:26 PM
  • Comment added

• Feature STC-299: Additional protections for restricted comments in places where comments are accessed
  updated by Bruno Pagno on 04/08/2025 11:06 AM
  • Description changed (Details)
• Open Point STC-300: How to handle exposing internal comments on the API?
  created by Bruno Pagno on 04/08/2025 10:59 AM
• Task STC-298: Scenarios that need manual QA to ensure restricted comments are protected
  updated by Kabiru Mwenja on 04/08/2025 10:56 AM
  • Parent set to Additional protections for internal comments in places where comments are accessed
• Feature STC-299: Additional protections for restricted comments in places where comments are accessed
  created by Kabiru Mwenja on 04/08/2025 10:54 AM
  • Comment added

    Updated automatically by changing values within child work package STC-298

• Task STC-298: Scenarios that need manual QA to ensure restricted comments are protected
  updated by Bruno Pagno on 04/08/2025 10:54 AM
  • Description changed (Details)
• Task STC-298: Scenarios that need manual QA to ensure restricted comments are protected
  created by Kabiru Mwenja on 04/08/2025 10:31 AM
• Open Point STC-294: Should we introduce a project setting to make comments restricted by default?
  updated by Parimal Satyal on 04/08/2025 09:41 AM
  • Subject changed from Should we delay email notifications to avoid potential leaks of restricted visibility comments from user error
    to Should we introduce a project setting to make comments restricted by default?
• Feature STC-295: Show warning if a user tries to 'unrestrict' a restricted-visibility comment when there's text in the comment box
  updated by Parimal Satyal on 04/08/2025 09:35 AM
  • Description changed (Details)
• Bug STC-297: Leaking restricted comments when polling
  updated by Bruno Pagno on 04/08/2025 09:12 AM
  • Status changed from in development to needs review
  • Assignee deleted (Bruno Pagno)
• Bug STC-297: Leaking restricted comments when polling
  updated by GitHub ⁤ on 04/08/2025 09:12 AM
  • Comment added

• Bug STC-297: Leaking restricted comments when polling
  created by Bruno Pagno on 04/08/2025 09:10 AM
• Feature STC-256: Group work package-related project settings in a new entry called 'Work packages'
  updated by Corinna Günther on 04/08/2025 08:38 AM
  • Comment added

    Hi Parimal Satyal, this feature affects Community users as well, right? I'm only asking because the parent is an Enterpr...

04/07/2025

• Feature STC-230: Cosmetic UI optimisations to the emoji reactions
  updated by Ivan Kuchin on 04/07/2025 07:19 PM
  • Comment added

    Parimal Satyal wrote:
    Reduce horizontal spacing: Yes, looks better. Could you specify what the new spacing is?
    It i...

• Implementation STC-205: Ensure notifications work in both restricted and unrestricted state independent of permission changes
  updated by Bruno Pagno on 04/07/2025 05:30 PM
  • Assignee changed from Kabiru Mwenja to Bruno Pagno
• Feature STC-230: Cosmetic UI optimisations to the emoji reactions
  updated by Parimal Satyal on 04/07/2025 12:10 PM
  • The changes were retracted.
• Epic SISMI-1: Automatically create work packages by email - map IMAP inbox with work packages attributes
  updated by Niels Lindenthal on 04/07/2025 11:53 AM
  • Description changed (Details)
  • Out of scope set (Details)
  • Acceptance criteria set (Details)
• Implementation STC-208: Add capability to enable and disable work package comment with restricted visibility at project level
  updated by Kabiru Mwenja on 04/07/2025 10:51 AM
  • Status changed from in development to in review
  • Assignee changed from Bruno Pagno to Kabiru Mwenja