10/09/2025

• Implementation FPCV-33: Switch from section based editing to one modal per attribute
  updated by Attila Dombi on 10/09/2025 05:16 PM
  • Description changed (Details)
• Open Point FPCV-51: Should we display a disabled tooltip with the reason?
  updated by Attila Dombi on 10/09/2025 05:14 PM
  • Status changed from new to decided
  • % Complete set to 100%
  • Decision set to Yes: "Non-editable attribute. This value is calculated automatically"
• Open Point FPCV-51: Should we display a disabled tooltip with the reason?
  updated by Marc Alcobé on 10/09/2025 02:17 PM
  • Comment added

    HI Attila Dombi,
    Great question, yes I would expect a tooltip to be displayed on hover explaining why it is not editable...

• Implementation FPCV-33: Switch from section based editing to one modal per attribute
  updated by Attila Dombi on 10/09/2025 01:19 PM
  • Comment added

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

  • Description changed (Details)
  • Scheduling mode set to Automatic
• Open Point FPCV-51: Should we display a disabled tooltip with the reason?
  created by Attila Dombi on 10/09/2025 01:19 PM

10/08/2025

• Implementation FPCV-33: Switch from section based editing to one modal per attribute
  updated by Attila Dombi on 10/08/2025 08:39 PM
  • Assignee set to Attila Dombi

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