Review main Merged

91007[FEATURE] Improve Scheduler task group handling and display

Oli Bartsch CR +2 V +2 Hard +248 −356 updated 10/17/25, 09:00

Commit message

This introduces several enhancements to
the scheduler module's task group functionality:

- Adds a new color field to task groups, allowing
  administrators to assign colors for visual distinction

- Displays assigned colors as left border on group panels

- Makes group names clickable links for quick editing of
  group properties (name, color, description)

- Displays group descriptions directly in the scheduler module

The color field includes a value picker with predefined
TYPO3 brand colors and common color options, making it
easy to assign colors without manually entering hex values.

These improvements enhance the usability and organization
of the scheduler module, particularly for installations
managing many task groups.

Review

  • Code review CR +2 Done
    • Oli Bartsch +2
    • Garvin Hicking +1
    • Lina Wolf +1
  • Verified V +2 Done
    • Oli Bartsch +2
    • Garvin Hicking +1
    • Lina Wolf +1
    • core-ci +1 CI

Issues 1

Files 16

Review log 2637

Show 912 earlier messages
  1. Oli Bartsch uploaded patch set 1 10/10/25, 20:52

  2. core-ci voted on patch set 1 V -1 10/10/25, 21:00 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86439

  3. Oli Bartsch uploaded patch set 2 V -1 10/11/25, 08:19

  4. core-ci voted on patch set 2 V -1 10/11/25, 08:28 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86457

  5. Oli Bartsch uploaded patch set 3 V -1 10/11/25, 08:45

  6. core-ci voted on patch set 3 V +1 10/11/25, 08:53 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86460

  7. Lina Wolf commented on patch set 3 10/12/25, 09:02

    I wonder how this change is considered A11y wise. Meaning should not be transported by color (thinking of color blind etc) and how can we prevent color combinations without sufficient contrast?
  8. Garvin Hicking commented on patch set 3 10/12/25, 12:51

    Reply

    I would argue the color is purely cosmetical, as the meaning is transported via the group name already?
  9. Garvin Hicking commented on patch set 3 10/12/25, 12:53

    Reply

    functionality-wise, every task group is the same, so there's two options of distinction: color and text. We could argue whether an icon would make sense here?
  10. Lina Wolf commented on patch set 3 V +1 10/12/25, 13:52

    Yeah, I had a look at it in rendered form and I think it should be fine a11y wise. The color does not transport meaning but is just another visual guide and also there is no danger of missing contrast destroying meaning
  11. Lina Wolf commented on patch set 3 CR +1 10/12/25, 13:54

    Code also looks good
  12. Garvin Hicking commented on patch set 3 10/12/25, 16:48

    Feature-107668-ImproveSchedulerTaskGroupHandlingAndDisplay.rst:52

    We should add a note here that TCA overrides are possible for custom color arrangements, and give a code example

    locallang_tca.xlf:77

    I think we should also have a grey / black color to indicate something like "not important groups"?

    GroupUnusedList.html:17

    I know we have several places in the core already that use inline styles which make restricting the CSP harder, so I wonder if we might have any way to prevent inline style? A webcomponent with dynamic colors? Emit+cache the existing colors and giving them names to refer to in CSS? Dynamically added CSS via the PageRenderer?

    TaskList.html:106

    (see other inline style note)

    TaskList.html:118

    We only have 5 places in the core that use `<i>` - I think we should try to avoid this in favor of `<em>` which is more common in the core?

    TaskGroupColorTest.php:32

    Hm these only really tests if database inserts work? I wonder if we should instead do a functional tests that checks that the scheduler group listing contains the color that has been assigned in the HTML output.
  1. Garvin Hicking commented on patch set 3 10/12/25, 16:49

    Should we align the border width to match the inline info boxes? See screenshot: https://www.dropbox.com/scl/fi/m9qebvlsttc2ibxvdv5x6/Screenshot-2025-10-12-at-18.48.38.png?rlkey=pwqvv0ldkbzf8saa7hvwes1wk&dl=0 it looks a bit "off" when I see these mismatching by a few pixels, so it feels a bit uneven?
  2. Garvin Hicking commented on patch set 3 10/12/25, 16:51

    The button to create a new group only asks for a name. I think that modal should add some small text like "Tip: You can assign colors to groups if you edit the group". Assigning the colour within the modal popup would probably be a lot of work, and then we should also ask for the description. ... then again, maybe get rid of the modal alltogether and directly lead to the TCA "create new record" mask?
  3. Chris Müller commented on patch set 3 10/12/25, 17:08

    TaskList.html:118 Reply

    I think, it depends: If the text has semantical meaning ("em" means emphasize), you are right. If this is just setting the text italic, because of ..., then "i" should be sufficient IMHO.
  4. Oli Bartsch uploaded patch set 4 CR +1 V +1 10/13/25, 14:52

  5. core-ci voted on patch set 4 V -1 10/13/25, 15:00 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86554

  6. Oli Bartsch commented on patch set 4 10/13/25, 15:02

    Reply

    No, I have used the 4px according to the labels in the page tree. I tried 8px but this looks odd in my eyes.

    Reply

    I've added a small hint with a button to edit the whole record, which also forwards an already entered group name.

    Feature-107668-ImproveSchedulerTaskGroupHandlingAndDisplay.rst:52 Reply

    Done

    locallang_tca.xlf:77 Reply

    I've added al colors from our Styleguide "Color Tokens", including gray.

    GroupUnusedList.html:17 Reply

    THB the complete form engine is based on inline styles. Let's not misuse this patch for such reworks. This should be done in a whole in a separate patch.

    TaskList.html:106 Reply

    See other comment

    TaskList.html:118 Reply

    I think `<i>` is fine here as it is really only about the display without any meaning, similar to the pagination in the file list, which also uses `<i>`.

    TaskGroupColorTest.php:32 Reply

    You are right, test makes no sense at all. Replaced this by proper acceptance tests.
  7. core-ci commented on patch set 4 10/13/25, 15:04 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86554

  8. core-ci commented on patch set 4 10/13/25, 15:13 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86554

  9. Oli Bartsch rebased onto patch set 5 V -1 10/13/25, 15:14

  10. core-ci voted on patch set 5 V -1 10/13/25, 15:23 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86558

  11. Garvin Hicking commented on patch set 5 10/13/25, 15:36

    GroupUnusedList.html:17 Reply

    Sure. But it's imo worth to discuss these shortcomings when they show up, just to maybe add an issue if someone agrees this could be worth addressing.
  12. Oli Bartsch uploaded patch set 6 V -1 10/13/25, 15:55

  13. core-ci voted on patch set 6 V -1 10/13/25, 16:07 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86567

  14. Oli Bartsch uploaded patch set 7 V -1 10/13/25, 21:11

  15. core-ci voted on patch set 7 V +1 10/13/25, 21:18 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86581

  16. Oli Bartsch uploaded patch set 8 V +1 10/13/25, 21:21

  17. core-ci voted on patch set 8 V +1 10/13/25, 21:29 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86582

  18. Garvin Hicking voted on patch set 8 CR +1 V +1 10/13/25, 21:50

  19. Oli Bartsch uploaded patch set 9 CR +1 V +1 10/14/25, 07:54

  20. core-ci voted on patch set 9 V +1 10/14/25, 08:03 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86603

  21. Garvin Hicking voted on patch set 9 CR +1 V +1 10/14/25, 08:10

  22. Lina Wolf voted on patch set 9 CR +1 V +1 10/15/25, 07:39

  23. Oli Bartsch voted on patch set 9 CR +2 V +2 10/15/25, 08:00

  24. Oli Bartsch merged patch set 10 10/15/25, 08:01

  25. Lina Wolf commented on patch set 10 10/17/25, 09:00

    Unresolved

    Please review related documentation: https://review.typo3.org/c/Packages/TYPO3.CMS/+/91121