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...

02/25/2025

• Bug SDS-229: Useless confirmation dialog for canceling editing of work package
  updated by Oliver Günther on 02/25/2025 08:19 PM
  • Comment added

    Duplicate of OP-16567 and OP-16531

  • Status changed from confirmed to rejected
• Task SDS-227: Form input: introduce a smaller input size for date/time
  updated by Parimal Satyal on 02/25/2025 07:00 PM
  • Comment added

    Hi Marc Alcobé. 
    This is to follow-up on our discussion with Niels this morning. Does this look okay to you?
    Cheers
    Pari...

  • Description set (Details)
  • Status changed from new to needs clarification
  • Assignee set to Parimal Satyal
  • File 1_0_00_-_Lifecycle_modal.png added as attachment
  • Designer set to Parimal Satyal
• Bug SDS-229: Useless confirmation dialog for canceling editing of work package
  created by Wieland Lindenthal on 02/25/2025 05:18 PM
  • Comment added

    Oliver Günther I remember that you were working on something similar. Do you know something more about this? Feel free t...

• Bug SDS-228: Regression: Rich text headlines show link icon on hover before the headline, while rendering after would be correct
  created by Wieland Lindenthal on 02/25/2025 05:11 PM
  • Comment added

    Henriette Darge May I assign it to you for delegation? I added the priority to high as I find it really disturbing/annoy...

• Task SDS-227: Form input: introduce a smaller input size for date/time
  created by Parimal Satyal on 02/25/2025 04:55 PM
• Task SDS-224: Create component "Meeting Status"
  updated by Parimal Satyal on 02/25/2025 04:53 PM
  • Description changed (Details)
  • File OP_Status_Figma_2.png added as attachment
• Task SDS-222: Determine Assistive Technology tooling needs for designer, dev and QA team
  updated by Alexander Coles on 02/25/2025 03:51 PM
  • Status changed from new to in progress
  • Assignee set to Alexander Coles
  • Start date set to 02/25/2025
  • Designer set to Parimal Satyal
• Task SDS-222: Determine Assistive Technology tooling needs for designer, dev and QA team
  updated by Cécile Guiot on 02/25/2025 03:47 PM
  • Comment added

    Alexander Coles it was a front-end bug, but not an a11y bug. I also can't remember if it was a Primer or Angular bug.

• Task SDS-223: Find out what Assistive Technologies our users are using - and marketshare
  updated by Alexander Coles on 02/25/2025 03:45 PM
  • Comment added

    Parimal Satyal Again, I've updated the description accordingly.
    Although I don't think this stops us making a start on s...

  • Description changed (Details)
  • Status changed from new to in progress
  • Assignee set to Alexander Coles
  • Start date set to 02/25/2025
• Task SDS-222: Determine Assistive Technology tooling needs for designer, dev and QA team
  updated by Alexander Coles on 02/25/2025 03:44 PM
  • Comment added

    Cécile Guiot interesting. was that specifically an accessibility bug?
    Regarding access to Windows generally, I totally a...

• Task SDS-222: Determine Assistive Technology tooling needs for designer, dev and QA team
  updated by Cécile Guiot on 02/25/2025 03:36 PM
  • Comment added

    Alexander Coles one thought i have but no data to support it: we might want Parrallels with a Windows 10/11 Pro license,...

• Task SDS-222: Determine Assistive Technology tooling needs for designer, dev and QA team
  updated by Alexander Coles on 02/25/2025 03:23 PM
  • Comment added

    Parimal Satyal  amended subject accordingly.

  • Subject changed from Determine Assistive Technology tooling needs for devs and QA to Determine Assistive Technology tooling needs for designer, dev and QA team
• Task SDS-223: Find out what Assistive Technologies our users are using - and marketshare
  updated by Parimal Satyal on 02/25/2025 03:21 PM
  • Comment added

    Hi Alexander Coles,
    FYI, on the Product/Design end, we also intend to run a user test for the new date picker and intend...

• Bug SDS-214: Users in lists miss popover
  updated by Ivana Šugić on 02/25/2025 01:41 PM
  • Comment added

    Issue has been fixed for points 3, 4 and 5 (see this comment) ✅ 
    Tested on:
    Ubuntu 22.04.5 LTS
    Chrome 133.0.6943.98

  • Status changed from in test to closed
  • Assignee deleted (Ivana Šugić)
• Task SDS-224: Create component "Meeting Status"
  updated by Parimal Satyal on 02/25/2025 12:52 PM
  • Comment added

    The OP Status component is now defined in Figma and here. Let's discuss this when Henriette Darge is back to agree on:
    ...

  • Description changed (Details)
  • Status changed from needs clarification to in progress
  • File OP_Status_Figma.png added as attachment
• Open Point SDS-226: Should we introduce a form component, that has a common max-width for all settings forms?
  updated by Eric Schubert on 02/25/2025 12:51 PM
  • Comment added

    As discussed in https://community.openproject.org/projects/gmbh/meetings/4419:
    I will implement a draft
    general appr...

• Bug SDS-214: Users in lists miss popover
  updated by Ivana Šugić on 02/25/2025 10:20 AM
  • Status changed from merged to in test
  • Assignee set to Ivana Šugić
• Task SDS-224: Create component "Meeting Status"
  updated by Parimal Satyal on 02/25/2025 10:08 AM
  • Description changed (Details)

02/24/2025

• Bug SDS-214: Users in lists miss popover
  updated by GitHub ⁤ on 02/24/2025 05:45 PM
  • Comment added

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

• Open Point SDS-226: Should we introduce a form component, that has a common max-width for all settings forms?
  created by Eric Schubert on 02/24/2025 05:35 PM
• Code maintenance SDS-225: Harmonize form spacing and position on settings pages
  created by Eric Schubert on 02/24/2025 05:34 PM
• Bug SDS-214: Users in lists miss popover
  updated by Tobias Dillmann on 02/24/2025 05:08 PM
  • Status changed from review approved to merged
• Bug SDS-214: Users in lists miss popover
  updated by GitHub ⁤ on 02/24/2025 05:07 PM
  • Comment added

• Bug SDS-214: Users in lists miss popover
  updated by Behrokh Satarnejad on 02/24/2025 04:32 PM
  • Status changed from in review to review approved
  • Assignee deleted (Behrokh Satarnejad)
• Task SDS-224: Create component "Meeting Status"
  created by Parimal Satyal on 02/24/2025 04:00 PM
• Bug SDS-214: Users in lists miss popover
  updated by Behrokh Satarnejad on 02/24/2025 02:00 PM
  • Status changed from needs review to in review
• Bug SDS-214: Users in lists miss popover
  updated by Jens Ulferts on 02/24/2025 11:22 AM
  • Assignee set to Behrokh Satarnejad
• Bug SDS-221: Danger Dialog and Feedback Dialog close button ARIA label is not localised
  updated by Henriette Darge on 02/24/2025 10:51 AM
  • Comment added

    We discussed that with the product team and decided to propose a change upstream to make that localisable.

  • Version set to 15.4.0
• Bug SDS-214: Users in lists miss popover
  updated by Tobias Dillmann on 02/24/2025 09:03 AM
  • Comment added

    In the above PR, all mentioned missing hover cards are fixed. With two exceptions:
    Time and cost user filter list
    "M...

  • Status changed from in development to needs review
  • Assignee deleted (Tobias Dillmann)
• Bug SDS-214: Users in lists miss popover
  updated by GitHub ⁤ on 02/24/2025 08:58 AM
  • Comment added