10/14/2025

• Bug FPCV-53: Wrong urls used on some custom field/page attribute admin pages
  created by Ivan Kuchin on 10/14/2025 06:13 PM
• Implementation FPCV-12: Allow usage of custom fields of type Scored List within a calculated values formula
  updated by Jens Ulferts on 10/14/2025 04:57 PM
  • Status changed from in review to review failed
  • Assignee changed from Jens Ulferts to Ivan Kuchin
• Bug FPCV-52: Updating the formula takes long after "Save" on larger instances
  created by Jens Ulferts on 10/14/2025 04:38 PM
• Implementation FPCV-12: Allow usage of custom fields of type Scored List within a calculated values formula
  updated by Jens Ulferts on 10/14/2025 01:23 PM
  • Status changed from needs review to in review

10/13/2025

• 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/13/2025 01:42 PM
  • Status changed from in development to needs review
• Implementation FPCV-33: Switch from section based editing to one modal per attribute
  updated by Attila Dombi on 10/13/2025 01:10 PM
  • Status changed from in specification to in development
• 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/13/2025 11:54 AM
  • Assignee deleted (Attila Dombi)

10/10/2025

• Implementation FPCV-12: Allow usage of custom fields of type Scored List within a calculated values formula
  updated by Jens Ulferts on 10/10/2025 01:57 PM
  • Assignee set to Jens Ulferts
• Implementation FPCV-12: Allow usage of custom fields of type Scored List within a calculated values formula
  updated by Ivan Kuchin on 10/10/2025 12:59 PM
  • Status changed from in development to needs review
  • Assignee deleted (Ivan Kuchin)

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