10/07/2025

• Epic FPCV-1: Calculate project priority scores based on project attributes
  updated by Niels Lindenthal on 10/07/2025 01:51 PM
  • Comment added

    Updated automatically by changing values within child work package FPCV-4

  • Total work changed from 180d 0h to 220d 0h
  • Scheduling mode set to Manual
  • Total % complete changed from 0% to 18%
• Feature FPCV-4: Sorting and filtering on project scores
  updated by Niels Lindenthal on 10/07/2025 01:50 PM
  • Type changed from Epic to Feature
  • Parent set to Calculate project priority scores based on project attributes
  • PD (min) changed from 20 to 20.0
  • PD (max) changed from 20 to 20.0
  • Acceptance criteria deleted (Details)
  • Roadmap deleted ((deleted option))
• Implementation FPCV-50: "Required for all projects" should not require a value to be set for a Calculated Value
  updated by GitHub ⁤ on 10/07/2025 01:17 PM
  • Comment added

10/06/2025

• Implementation FPCV-12: Allow usage of custom fields of type Scored List within a calculated values formula
  updated by Ivan Kuchin on 10/06/2025 04:52 PM
  • Status changed from review failed to in development
  • Developers changed from Tobias Dillmann to Ivan Kuchin
• Implementation FPCV-12: Allow usage of custom fields of type Scored List within a calculated values formula
  updated by Ivan Kuchin on 10/06/2025 02:56 PM
  • Assignee set to Ivan Kuchin
• Implementation FPCV-13: Recalculate when a score of a Scored List is changed within the administration
  updated by Ivan Kuchin on 10/06/2025 02:56 PM
  • Assignee changed from Tobias Dillmann to Ivan Kuchin

10/02/2025

• Implementation FPCV-12: Allow usage of custom fields of type Scored List within a calculated values formula
  updated by Ivan Kuchin on 10/02/2025 07:34 PM
  • Status changed from in review to review failed
  • Assignee deleted (Ivan Kuchin)
• Implementation FPCV-12: Allow usage of custom fields of type Scored List within a calculated values formula
  updated by Ivan Kuchin on 10/02/2025 02:52 PM
  • Status changed from needs review to in review
• Implementation FPCV-13: Recalculate when a score of a Scored List is changed within the administration
  updated by GitHub ⁤ on 10/02/2025 02:43 PM
  • Comment added

10/01/2025

• Implementation FPCV-50: "Required for all projects" should not require a value to be set for a Calculated Value
  updated by GitHub ⁤ on 10/01/2025 07:37 PM
  • Comment added

• Implementation FPCV-50: "Required for all projects" should not require a value to be set for a Calculated Value
  updated by Attila Dombi on 10/01/2025 07:18 PM
  • Comment added

    Claiming this work package, because it will be solved in by design.

  • Status changed from specified to in development
  • Assignee set to Attila Dombi
  • Developers changed from OP Dev Polaris Team to Attila Dombi
• Implementation FPCV-13: Recalculate when a score of a Scored List is changed within the administration
  updated by Tobias Dillmann on 10/01/2025 05:29 PM
  • Status changed from new to in development
  • Assignee set to Tobias Dillmann
  • Developers changed from OP Dev Polaris Team to Tobias Dillmann, OP Dev Polaris Team
• Bug FPCV-47: Limit number precision when displaying Calculated Values
  updated by Tobias Dillmann on 10/01/2025 03:09 PM
  • Bug found in version set to 16.6.x
• Implementation FPCV-50: "Required for all projects" should not require a value to be set for a Calculated Value
  created by Tobias Dillmann on 10/01/2025 02:25 PM
• Implementation FPCV-12: Allow usage of custom fields of type Scored List within a calculated values formula
  updated by Jens Ulferts on 10/01/2025 02:13 PM
  • Assignee set to Ivan Kuchin
• Bug FPCV-47: Limit number precision when displaying Calculated Values
  updated by Ivana Šugić on 10/01/2025 01:24 PM
  • Comment added

    Fixed ✅ 
    Tested on:
    Core build
    7cb543f3ddfdb28943904b6b1a459a62b3223117
    Product version
    4306063c40b4c7c2b944868849081344...

  • Status changed from in test to closed
  • Assignee deleted (Ivana Šugić)
  • % Complete set to 100%
• Bug FPCV-47: Limit number precision when displaying Calculated Values
  updated by GitHub ⁤ on 10/01/2025 11:45 AM
  • Comment added

    opf/openproject#20450 deployed to qa.openproject-stage.com

• Bug FPCV-47: Limit number precision when displaying Calculated Values
  updated by Ivana Šugić on 10/01/2025 11:05 AM
  • Status changed from merged to in test
  • Assignee set to Ivana Šugić
• Bug FPCV-47: Limit number precision when displaying Calculated Values
  updated by Tobias Dillmann on 10/01/2025 11:00 AM
  • Status changed from review approved to merged
• Bug FPCV-47: Limit number precision when displaying Calculated Values
  updated by GitHub ⁤ on 10/01/2025 10:59 AM
  • Comment added

• Bug FPCV-47: Limit number precision when displaying Calculated Values
  updated by Ivan Kuchin on 10/01/2025 10:24 AM
  • Status changed from in review to review approved
  • Assignee deleted (Ivan Kuchin)
• Bug FPCV-47: Limit number precision when displaying Calculated Values
  updated by Tobias Dillmann on 10/01/2025 10:04 AM
  • Status changed from needs review to in review