03/04/2025

• Code maintenance SDS-233: Separate component definition from patterns in the lookbook
  updated by Cécile Guiot on 03/04/2025 04:32 PM
  • Status changed from tested to closed
  • % Complete set to 100%
• Feature SDS-224: Create component Status button based on Action menu
  updated by Cécile Guiot on 03/04/2025 04:31 PM
  • Status changed from tested to closed
  • % Complete set to 100%
• Bug SDS-205: Missing breadcrumb in Times & Cost Administration
  updated by Cécile Guiot on 03/04/2025 04:31 PM
  • Status changed from tested to closed
  • % Complete set to 100%
• Open Point SDS-226: Should we introduce a form component, that has a common max-width for all settings forms?
  updated by Alexander Coles on 03/04/2025 02:35 PM
  • The changes were retracted.
• Open Point SDS-226: Should we introduce a form component, that has a common max-width for all settings forms?
  updated by GitHub ⁤ on 03/04/2025 02:00 PM
  • Comment added

• Feature SDS-234: Primerize Project create form and settings -> Information
  updated by Marc Alcobé on 03/04/2025 12:23 PM
  • Comment added

    Hi Niels Lindenthal and Oliver Günther,
    I've created some new mockups with the Primarised version of both the Informatio...

  • Mockups set to https://www.figma.com/design/k8FvtPsyKrbqII2tHg0M0q/Project-Information?node-id=0-1
• Feature SDS-234: Primerize Project create form and settings -> Information
  updated by Henriette Darge on 03/04/2025 11:11 AM
  • Description changed (Details)
• Feature SDS-234: Primerize Project create form and settings -> Information
  updated by Oliver Günther on 03/04/2025 11:09 AM
  • Assignee deleted (Oliver Günther)
• Feature SDS-234: Primerize Project create form and settings -> Information
  updated by Henriette Darge on 03/04/2025 11:08 AM
  • Description changed (Details)
• Feature SDS-234: Primerize Project create form and settings -> Information
  updated by Oliver Günther on 03/04/2025 10:39 AM
  • Type changed from Code maintenance to Feature
  • Subject changed from Primerize Project settings -> Information to Primerize Project create form and settings -> Information
  • Status changed from in specification to specified
• Code maintenance SDS-234: Primerize Project settings -> Information
  updated by Niels Lindenthal on 03/04/2025 08:38 AM
  • Comment added

    Hi Marc Alcobé,
    Thanks for your mockup. Based on this futuristic concept can you please create another version with the ...

• Code maintenance SDS-234: Primerize Project settings -> Information
  updated by Niels Lindenthal on 03/04/2025 08:26 AM
  • Comment added

    Hi Oliver Günther,
    Yes, let's do that. Do you want me to create a separate work package for the project create form?
    Bes...

  • Description changed (Details)
  • Status changed from new to in specification
• Code maintenance SDS-234: Primerize Project settings -> Information
  updated by Oliver Günther on 03/04/2025 08:20 AM
  • Comment added

    Hi Niels Lindenthal Marc Alcobé , if we primerize the project settings, the project creation form should be primerized a...

03/03/2025

• Code maintenance SDS-234: Primerize Project settings -> Information
  updated by Niels Lindenthal on 03/03/2025 11:04 PM
  • Comment added

    Thanks Marc Alcobé,
    I added some comments

  • Assignee set to Oliver Günther
  • Requires doc change changed from No to Yes
• Code maintenance SDS-234: Primerize Project settings -> Information
  updated by Marc Alcobé on 03/03/2025 04:51 PM
  • Comment added

    Hi Niels Lindenthal,
    I've created an approach for moving all project attributes available in the Project Settings > I...

• Epic SDS-166: Apply standardized component for PageHeaders & SubHeaders in the missing rails based pages
  updated by Henriette Darge on 03/03/2025 12:35 PM
  • Roadmap changed from (deleted option) to (deleted option)
• Epic SDS-176: Apply standardized component for PageHeaders & SubHeaders in the missing angular based pages
  updated by Niels Lindenthal on 03/03/2025 09:51 AM
  • Enterprise plan set to Community
• Epic SDS-166: Apply standardized component for PageHeaders & SubHeaders in the missing rails based pages
  updated by Niels Lindenthal on 03/03/2025 09:51 AM
  • Enterprise plan set to Community
• Epic SDS-45: Apply standardized component for PageHeaders & SubHeaders in the WorkPackage pages
  updated by Niels Lindenthal on 03/03/2025 09:50 AM
  • Enterprise plan set to Community

02/28/2025

• Feature SDS-236: Provide keyboard shortcuts (mnemonics) to operate Danger and Feedback Dialogs
  updated by Alexander Coles on 02/28/2025 03:53 PM
  • Priority changed from Medium to Low
• Code maintenance SDS-233: Separate component definition from patterns in the lookbook
  updated by Cécile Guiot on 02/28/2025 03:47 PM
  • Comment added

    All set ✅
    Tested on:
    Core build
    0cf53f51afeba174fb3e2405365e80e592169866
    Product version
    79e94fc8ce0c56340ccde1cb1ab1463...

  • Status changed from in test to tested
• Code maintenance SDS-233: Separate component definition from patterns in the lookbook
  updated by GitHub ⁤ on 02/28/2025 03:45 PM
  • Comment added

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

• Task SDS-222: Determine Assistive Technology tooling needs for designer, dev and QA team
  updated by Henriette Darge on 02/28/2025 03:34 PM
  • Description changed (Details)
• Feature SDS-236: Provide keyboard shortcuts (mnemonics) to operate Danger and Feedback Dialogs
  created by Alexander Coles on 02/28/2025 02:41 PM
• Feature SDS-235: Advanced accessibility for the Danger Dialogs (with ARIA semantics to communicate contextual changes)
  created by Alexander Coles on 02/28/2025 02:36 PM
• Code maintenance SDS-234: Primerize Project settings -> Information
  created by Niels Lindenthal on 02/28/2025 02:01 PM
  • Comment added

    Hi Marc Alcobé,
    Can you please prepare mockups for this?
    Thanks
    Niels

• Code maintenance SDS-233: Separate component definition from patterns in the lookbook
  updated by Cécile Guiot on 02/28/2025 01:42 PM
  • Status changed from merged to in test
• Code maintenance SDS-233: Separate component definition from patterns in the lookbook
  updated by Henriette Darge on 02/28/2025 12:29 PM
  • Status changed from review approved to merged
• Code maintenance SDS-233: Separate component definition from patterns in the lookbook
  updated by GitHub ⁤ on 02/28/2025 12:29 PM
  • Comment added

• Code maintenance SDS-233: Separate component definition from patterns in the lookbook
  updated by Alexander Coles on 02/28/2025 11:55 AM
  • Subject changed from Separte component definition from patterns in the lookbook to Separate component definition from patterns in the lookbook
  • Status changed from needs review to review approved
  • Assignee deleted (Alexander Coles)
• Code maintenance SDS-233: Separte component definition from patterns in the lookbook
  updated by Jens Ulferts on 02/28/2025 11:21 AM
  • Assignee set to Alexander Coles

02/27/2025

• Feature SDS-224: Create component Status button based on Action menu
  updated by Cécile Guiot on 02/27/2025 04:07 PM
  • Comment added

    Working as expected (or rather looking as expected hehe) ✅
    Tested on the lookbook:
    Core build
    eae6ee18b14f954e3cb718c619...

  • Status changed from in test to tested
  • Assignee deleted (Cécile Guiot)
• Feature SDS-224: Create component Status button based on Action menu
  updated by Henriette Darge on 02/27/2025 02:08 PM
  • Description changed (Details)
• Feature SDS-224: Create component Status button based on Action menu
  updated by Cécile Guiot on 02/27/2025 02:02 PM
  • Status changed from merged to in test
  • Assignee set to Cécile Guiot
• Feature SDS-224: Create component Status button based on Action menu
  updated by GitHub ⁤ on 02/27/2025 01:45 PM
  • Comment added

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

• Code maintenance SDS-233: Separte component definition from patterns in the lookbook
  updated by Henriette Darge on 02/27/2025 01:37 PM
  • Description changed (Details)
  • Status changed from in development to needs review
  • Assignee deleted (Henriette Darge)
• Code maintenance SDS-233: Separte component definition from patterns in the lookbook
  updated by GitHub ⁤ on 02/27/2025 01:36 PM
  • Comment added

• Code maintenance SDS-233: Separte component definition from patterns in the lookbook
  updated by Henriette Darge on 02/27/2025 01:16 PM
  • Description changed (Details)
  • Status changed from specified to in development
  • Accountable set to Henriette Darge
• Code maintenance SDS-230: Allow Sidepanel section to render ActionMenu
  updated by GitHub ⁤ on 02/27/2025 01:15 PM
  • Comment added

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

• Code maintenance SDS-230: Allow Sidepanel section to render ActionMenu
  updated by Oliver Günther on 02/27/2025 01:12 PM
  • Status changed from in test to closed
  • Assignee deleted (Cécile Guiot)
• Feature SDS-224: Create component Status button based on Action menu
  updated by Henriette Darge on 02/27/2025 01:06 PM
  • Comment added

    Hi Parimal Satyal 
    the linked figma design still show the rounded corners for the new StatusButton which we agreed not t...

  • Description changed (Details)
  • Status changed from review approved to merged
• Feature SDS-224: Create component Status button based on Action menu
  updated by GitHub ⁤ on 02/27/2025 01:06 PM
  • Comment added

• Code maintenance SDS-230: Allow Sidepanel section to render ActionMenu
  updated by GitHub ⁤ on 02/27/2025 01:01 PM
  • Comment added

• Code maintenance SDS-230: Allow Sidepanel section to render ActionMenu
  updated by GitHub ⁤ on 02/27/2025 12:03 PM
  • Comment added

• Code maintenance SDS-232: Adapt icon_for_color helper to respect color modes/themes
  updated by Henriette Darge on 02/27/2025 11:10 AM
  • Description changed (Details)
  • Version set to Product Backlog
• Code maintenance SDS-233: Separte component definition from patterns in the lookbook
  created by Henriette Darge on 02/27/2025 11:07 AM
• Code maintenance SDS-232: Adapt icon_for_color helper to respect color modes/themes
  created by Oliver Günther on 02/27/2025 11:05 AM
• Bug SDS-215: Popover missing in multi-select custom fields of type user
  updated by Ivana Šugić on 02/27/2025 11:04 AM
  • Assignee deleted (Ivana Šugić)
• Feature SDS-224: Create component Status button based on Action menu
  updated by Henriette Darge on 02/27/2025 11:02 AM
  • Status changed from needs review to review approved
• Code maintenance SDS-230: Allow Sidepanel section to render ActionMenu
  updated by Cécile Guiot on 02/27/2025 09:52 AM
  • Status changed from merged to in test
  • Assignee set to Cécile Guiot
• Feature SDS-224: Create component Status button based on Action menu
  updated by Oliver Günther on 02/27/2025 09:35 AM
  • Status changed from in development to needs review
  • Assignee deleted (Oliver Günther)
• Feature SDS-224: Create component Status button based on Action menu
  updated by GitHub ⁤ on 02/27/2025 09:24 AM
  • Comment added

• Feature SDS-224: Create component Status button based on Action menu
  updated by Oliver Günther on 02/27/2025 09:16 AM
  • Description changed (Details)

02/26/2025

• Open Point SDS-218: Should we continue using the 'pressed' state of buttons to indicate active status as we do today?
  updated by Parimal Satyal on 02/26/2025 09:33 PM
  • Comment added

    After a discussion with Marc, we're exploring the "Change of icon + colour fill with Primer tooltip" pattern we already ...

  • Description changed (Details)
  • File Favourite_project_pattern.png added as attachment
  • File Split_screen_active_state.png added as attachment
  • Decision set to Explore the "Change of icon + colour fill with Primer tooltip" option, especially for the sidebar/toolbar buttons which will be icon-only. This is a best mix of practical, usable with limited additional dev.
• Feature SDS-224: Create component Status button based on Action menu
  updated by Oliver Günther on 02/26/2025 04:42 PM
  • Status changed from in progress to in development
• Code maintenance SDS-230: Allow Sidepanel section to render ActionMenu
  updated by Oliver Günther on 02/26/2025 03:00 PM
  • Status changed from review approved to merged
• Bug SDS-228: Regression: Rich text headlines show link icon on hover before the headline, while rendering after would be correct
  updated by Henriette Darge on 02/26/2025 01:59 PM
  • Assignee deleted (Henriette Darge)
  • Version set to 15.4.0
• Code maintenance SDS-230: Allow Sidepanel section to render ActionMenu
  updated by GitHub ⁤ on 02/26/2025 11:38 AM
  • Comment added

• Code maintenance SDS-230: Allow Sidepanel section to render ActionMenu
  updated by Henriette Darge on 02/26/2025 11:32 AM
  • Status changed from needs review to review approved
  • Assignee deleted (OP Dev Dream Team)
• Open Point SDS-218: Should we continue using the 'pressed' state of buttons to indicate active status as we do today?
  updated by Parimal Satyal on 02/26/2025 11:16 AM
  • Comment added

    Next step: explore options similar to the favouriting projects on the Project list also for the split screen, i.e:
    Cha...

  • Description changed (Details)
  • Assignee set to Parimal Satyal
• Code maintenance SDS-230: Allow Sidepanel section to render ActionMenu
  updated by Oliver Günther on 02/26/2025 11:11 AM
  • Status changed from in development to needs review
  • Assignee changed from Oliver Günther to OP Dev Dream Team
• Code maintenance SDS-230: Allow Sidepanel section to render ActionMenu
  updated by GitHub ⁤ on 02/26/2025 11:11 AM
  • Comment added

• Code maintenance SDS-230: Allow Sidepanel section to render ActionMenu
  created by Oliver Günther on 02/26/2025 11:09 AM
• Feature SDS-224: Create component Status button based on Action menu
  updated by Parimal Satyal on 02/26/2025 10:28 AM
  • Comment added

    Proposal: Use a standard action button with just a colour input. Oliver will work with this, and Parimal will update Fig...

  • Type changed from Task to Feature
  • Subject changed from Create component "Meeting Status" to Create component Status button based on Action menu
  • Assignee changed from Parimal Satyal to Oliver Günther
  • Version set to 15.4.0
• Feature SDS-227: Form input: introduce a smaller input size for date/time
  updated by Parimal Satyal on 02/26/2025 10:19 AM
  • Type changed from Task to Feature
  • Description changed (Details)
  • Status changed from needs clarification to in specification
  • Version set to 15.4.0
• Task SDS-227: Form input: introduce a smaller input size for date/time
  updated by Marc Alcobé on 02/26/2025 09:53 AM
  • Comment added

    Hi Parimal Satyal,
    It works in theory. I would check first what is the longest date format supported and see if it reall...