10/28/2025

• Bug FPCV-58: Creating a calculated value project attribute marked required doesn't calculate values
  updated by Ivan Kuchin on 10/28/2025 08:27 PM
  • Status changed from in development to needs review
  • Assignee deleted (Ivan Kuchin)
• Bug FPCV-58: Creating a calculated value project attribute marked required doesn't calculate values
  updated by GitHub ⁤ on 10/28/2025 08:27 PM
  • Comment added

• Bug FPCV-58: Creating a calculated value project attribute marked required doesn't calculate values
  updated by Ivan Kuchin on 10/28/2025 04:26 PM
  • Status changed from confirmed to in development
  • Assignee set to Ivan Kuchin
  • Developers changed from OP Dev Polaris Team to Ivan Kuchin
• Bug FPCV-57: Impossible to create a project with required project attributes of type calculated value
  updated by Ivan Kuchin on 10/28/2025 04:21 PM
  • Status changed from needs clarification to rejected
  • % Complete set to 100%
• Code maintenance FPCV-61: Cleanup after calculated values
  created by Ivan Kuchin on 10/28/2025 04:01 PM
• Bug FPCV-59: Enabling calculated value by adding project to through custom field admin doesn't trigger calculation
  updated by Ivan Kuchin on 10/28/2025 02:24 PM
  • Status changed from in development to needs review
  • Assignee deleted (Ivan Kuchin)
• Bug FPCV-59: Enabling calculated value by adding project to through custom field admin doesn't trigger calculation
  updated by GitHub ⁤ on 10/28/2025 02:24 PM
  • Comment added

10/27/2025

• Code maintenance FPCV-60: CustomField#cast_value should delegate to CustomFieldFormat or should be removed
  created by Ivan Kuchin on 10/27/2025 08:15 PM
• Bug FPCV-54: undefined method 'full_messages' for an instance of Symbol in Admin::CustomFields::Hierarchy::ItemsController#destroy
  updated by Ivan Kuchin on 10/27/2025 05:22 PM
  • Comment added

    It is still odd to have a problem in code leading to 500, so probably better to just solve it in simplest way

• Bug FPCV-54: undefined method 'full_messages' for an instance of Symbol in Admin::CustomFields::Hierarchy::ItemsController#destroy
  updated by Attila Dombi on 10/27/2025 04:55 PM
  • Comment added

    Ivan Kuchin, tried to reproduce the issue via the UI, but it looks like the elements are always a leaf. Probably we don'...

• Bug FPCV-54: undefined method 'full_messages' for an instance of Symbol in Admin::CustomFields::Hierarchy::ItemsController#destroy
  updated by Ivan Kuchin on 10/27/2025 02:17 PM
  • Comment added

    Attila Dombi Were you able to somehow do it through UI or only from developer tools or console?

• Bug FPCV-56: Marking calculated value required for all projects doesn't calculate the value
  updated by Ivan Kuchin on 10/27/2025 02:12 PM
  • Status changed from review approved to merged
  • Assignee deleted (Attila Dombi)
• Bug FPCV-58: Creating a calculated value project attribute marked required doesn't calculate values
  updated by Jens Ulferts on 10/27/2025 10:30 AM
  • Developers set to OP Dev Polaris Team
• Bug FPCV-59: Enabling calculated value by adding project to through custom field admin doesn't trigger calculation
  updated by GitHub ⁤ on 10/27/2025 10:15 AM
  • Comment added

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

• Bug FPCV-56: Marking calculated value required for all projects doesn't calculate the value
  updated by GitHub ⁤ on 10/27/2025 10:15 AM
  • Comment added

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

10/26/2025

• Epic FPCV-1: Calculate project priority scores based on project attributes
  updated by Niels Lindenthal on 10/26/2025 10:14 AM
  • Finish date changed from 09/18/2025 to 12/04/2025
  • Priority changed from High to Medium
  • Duration changed from 51 days to 106 days
  • Roadmap changed from (deleted option) to 2025 Q4

10/24/2025

• Bug FPCV-59: Enabling calculated value by adding project to through custom field admin doesn't trigger calculation
  updated by GitHub ⁤ on 10/24/2025 08:32 PM
  • Comment added

• Bug FPCV-59: Enabling calculated value by adding project to through custom field admin doesn't trigger calculation
  updated by Ivan Kuchin on 10/24/2025 08:30 PM
  • Status changed from confirmed to in development
  • Assignee set to Ivan Kuchin
  • Developers set to Ivan Kuchin
• Implementation FPCV-50: "Required for all projects" should not require a value to be set for a Calculated Value
  updated by GitHub ⁤ on 10/24/2025 05:59 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/24/2025 04:42 PM
  • Description changed (Details)
• Bug FPCV-59: Enabling calculated value by adding project to through custom field admin doesn't trigger calculation
  updated by GitHub ⁤ on 10/24/2025 03:17 PM
  • Comment added

• Bug FPCV-56: Marking calculated value required for all projects doesn't calculate the value
  updated by GitHub ⁤ on 10/24/2025 03:16 PM
  • Comment added

• Bug FPCV-59: Enabling calculated value by adding project to through custom field admin doesn't trigger calculation
  created by Ivan Kuchin on 10/24/2025 03:08 PM
• 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/24/2025 02:50 PM
  • Description changed (Details)
• Bug FPCV-56: Marking calculated value required for all projects doesn't calculate the value
  updated by Jens Ulferts on 10/24/2025 01:28 PM
  • Parent set to Project attribute of type "Calculated value"
• Bug FPCV-58: Creating a calculated value project attribute marked required doesn't calculate values
  updated by Jens Ulferts on 10/24/2025 01:28 PM
  • Parent set to Project attribute of type "Calculated value"
• Bug FPCV-57: Impossible to create a project with required project attributes of type calculated value
  updated by Jens Ulferts on 10/24/2025 01:25 PM
  • Comment added

    Since marking the field as required will receive the meaning of always being active (with FPCV-50) and not of requiring ...

  • Parent set to Project attribute of type "Calculated value"
• Bug FPCV-56: Marking calculated value required for all projects doesn't calculate the value
  updated by Attila Dombi on 10/24/2025 12:06 PM
  • Status changed from in review to review approved
• Bug FPCV-56: Marking calculated value required for all projects doesn't calculate the value
  updated by Attila Dombi on 10/24/2025 10:53 AM
  • Status changed from needs review to in review
  • Assignee set to Attila Dombi

10/23/2025

• Bug FPCV-58: Creating a calculated value project attribute marked required doesn't calculate values
  created by Ivan Kuchin on 10/23/2025 07:22 PM
• Bug FPCV-57: Impossible to create a project with required project attributes of type calculated value
  updated by Ivan Kuchin on 10/23/2025 06:36 PM
  • Description changed (Details)
• Bug FPCV-56: Marking calculated value required for all projects doesn't calculate the value
  updated by Ivan Kuchin on 10/23/2025 05:58 PM
  • Status changed from confirmed to needs review
  • Developers set to Ivan Kuchin
• Bug FPCV-56: Marking calculated value required for all projects doesn't calculate the value
  updated by GitHub ⁤ on 10/23/2025 05:57 PM
  • Comment added

• Bug FPCV-56: Marking calculated value required for all projects doesn't calculate the value
  updated by Ivan Kuchin on 10/23/2025 05:55 PM
  • Subject changed from Marking calculated value required for all projects doesn't calculated the value to Marking calculated value required for all projects doesn't calculate the value
• Bug FPCV-57: Impossible to create a project with required project attributes of type calculated value
  created by Ivan Kuchin on 10/23/2025 04:22 PM
• Bug FPCV-56: Marking calculated value required for all projects doesn't calculated the value
  created by Ivan Kuchin on 10/23/2025 04:05 PM
• Feature FPCV-3: Project attribute of type "Calculated value"
  updated by Jens Ulferts on 10/23/2025 10:35 AM
  • Status changed from needs review to merged
• Feature FPCV-49: Allow inline-editing for project attributes
  updated by Jens Ulferts on 10/23/2025 10:30 AM
  • Comment added

    Turned into a feature because:
    The feature it was placed under will be released
    The implementation will be complex e...

  • Type changed from Implementation to Feature
  • Description changed (Details)
  • Version changed from 17.0.0 to 17.1.0
  • Parent changed from Project attribute of type "Calculated value" to Calculate project priority scores based on project attributes
  • Mockups set to https://www.figma.com/design/Ya9Xz4HvWCzOmM64qfvGPm/Projects-attributes?node-id=2573-7565
• 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/23/2025 10:25 AM
  • Status changed from review failed to in development
• Implementation FPCV-33: Switch from section based editing to one modal per attribute
  updated by GitHub ⁤ on 10/23/2025 10:15 AM
  • Comment added

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

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

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

• Implementation FPCV-50: "Required for all projects" should not require a value to be set for a Calculated Value
  updated by Oliver Günther on 10/23/2025 10:11 AM
  • Version deleted (16.6.0)
• Feature FPCV-3: Project attribute of type "Calculated value"
  updated by Jens Ulferts on 10/23/2025 12:34 AM
  • Status changed from in development to needs review
  • Assignee deleted (OP Dev Polaris Team)

10/22/2025

• Implementation FPCV-33: Switch from section based editing to one modal per attribute
  updated by Attila Dombi on 10/22/2025 09:54 PM
  • Status changed from review failed to closed
  • Assignee deleted (Attila Dombi)
  • % Complete set to 100%
• Implementation FPCV-33: Switch from section based editing to one modal per attribute
  updated by GitHub ⁤ on 10/22/2025 09:53 PM
  • Comment added

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

• Implementation FPCV-13: Recalculate when a score of a Scored List is changed within the administration
  updated by Jens Ulferts on 10/22/2025 11:54 AM
  • Status changed from review approved to closed
  • % Complete set to 100%