Shopware 6 Rule Builder UX Frustration: Community Highlights Critical Tagged Field Bug

Shopware 6 Rule Builder UX Frustration: Community Highlights Critical Tagged Field Bug

The Shopware community recently brought to light a significant user experience (UX) issue within the Shopware 6 backend's Rule Builder, specifically concerning the sw-tagged-field component. This discussion highlights a common frustration among merchants and developers when attempting to manage multiple values within rule conditions.

The original post, initiated by ZER0, detailed the severe usability problems: "Bitte einmal die UX im Rulebuilder fixen, das ist wirklich eine Zumutung: Man kann weder die Werte erkennen, noch - wenn mehrreihig dort durchscrollen oder überhaupt erkennen wieviele Werte hinterlegt sind… das macht die Bearbeitung unmöglich ohne jedesmal selbst das CSS im Browser zurechtzufummeln…" (Translated: "Please fix the UX in the Rulebuilder, it's really an imposition: You can neither see the values, nor scroll through them if there are multiple lines, or even tell how many values are stored… this makes editing impossible without constantly fiddling with the CSS in the browser…") An accompanying screenshot visually demonstrated the overlap and truncation of values, rendering the field practically unusable for complex rules.

The sentiment was echoed by R4M, who expressed surprise that such a critical issue would be discovered by users rather than Shopware's internal testing: "Interessant, das so etwas immer erst den Usern auffällt, aber Shopware selber offenbar nicht. Bin heute exakt über das selbe Problem auch gestolpert." (Translated: "It's interesting that users always notice such issues first, but Shopware itself apparently doesn't. I stumbled upon the exact same problem today.") This indicates a broad impact of the bug across the user base.

Crucially, the thread quickly led to an official response. Max_Shop linked to a newly created GitHub issue (shopware/shopware#21327) titled "Administration: sw-tagged-field is practically unusable." This issue, created by cramytech, provides further details, including a video clip demonstrating the problem on MacOS Safari, and clearly outlines the discrepancy between the actual and expected behavior: the inability to see and delete all entered values.

While awaiting an official fix, ZER0 mentioned a temporary "dirty quickfix" involving CSS z-index adjustments to make the field workable. This workaround, though not detailed in the thread, suggests that advanced users are resorting to browser-level modifications to bypass the immediate limitations.

Key Takeaways:

• A critical UX bug in the Shopware 6 Rule Builder's sw-tagged-field component prevents users from effectively managing multiple values.
• The issue impacts visibility, scrolling, and overall editing capabilities.
• Shopware has officially acknowledged the bug by creating a GitHub issue (#21327).
• A temporary CSS z-index adjustment is a known community workaround.

This community interaction underscores the importance of user feedback in identifying and addressing critical usability flaws in e-commerce platforms. The swift creation of a GitHub issue by Shopware demonstrates a responsive approach to community-reported problems, which is vital for maintaining a robust and user-friendly system.