Issue Summary

      When accessing Advanced Roadmaps features (Plans, Programs) while in Dark mode, a light background will be displayed.

      Steps to Reproduce

      1. On Jira, click on the profile icon at the top of the screen, then click on Theme > Dark
      2. Access an Advanced Roadmaps Plan or Program

      Expected Results

      The pages will be loaded in Dark mode.

      Actual Results

      A light background will be displayed.
       

      Workaround

      No workaround is available.

            [JSWSERVER-26178] Dark mode doesn't work on Advanced Roadmaps

            427d436cf927 - I'm writing regarding the classification of dark mode-related accessibility issues as you've mentioned in the previous comment, and tagged this ticket. I believe these issues should be classified as bugs rather than feature requests, and I'd like to explain our reasoning:

            1. The current situation represents a regression in accessibility and usability from our addon's previous baseline functionality. Users who enable dark mode - a core platform feature - are experiencing compromised readability with issues like light grey text on black backgrounds, which creates genuine accessibility barriers.
            2. These issues weren't introduced by new user requirements or changing standards, but rather emerged from the addon not being updated to maintain compatibility with Jira 10.3's dark mode implementation. Atlassian provided advance notice of this change, allowing time for necessary adaptations.
            3. When core functionality like readable text and proper contrast ratios are compromised, this represents a defect in the product rather than a missing feature. The fundamental issue isn't the addition of dark mode support, but rather fixing the broken accessibility and readability that resulted from not implementing proper support.
            4. From a user perspective, there's a reasonable expectation that addons will maintain compatibility with official platform features, especially those affecting basic usability and accessibility. The current situation represents a failure to meet this expectation.

            While implementing dark mode support does require development effort, the current accessibility issues are preventing users from effectively using existing functionality. This aligns with our standard definition of a bug - where existing features no longer work as intended for a subset of our users.

            I recommend we reclassify these issues as bugs with appropriate priority levels based on their severity and impact on user accessibility.

            Matthew Martin added a comment - 427d436cf927 - I'm writing regarding the classification of dark mode-related accessibility issues as you've mentioned in the previous comment, and tagged this ticket. I believe these issues should be classified as bugs rather than feature requests, and I'd like to explain our reasoning: The current situation represents a regression in accessibility and usability from our addon's previous baseline functionality. Users who enable dark mode - a core platform feature - are experiencing compromised readability with issues like light grey text on black backgrounds, which creates genuine accessibility barriers. These issues weren't introduced by new user requirements or changing standards, but rather emerged from the addon not being updated to maintain compatibility with Jira 10.3's dark mode implementation. Atlassian provided advance notice of this change, allowing time for necessary adaptations. When core functionality like readable text and proper contrast ratios are compromised, this represents a defect in the product rather than a missing feature. The fundamental issue isn't the addition of dark mode support, but rather fixing the broken accessibility and readability that resulted from not implementing proper support. From a user perspective, there's a reasonable expectation that addons will maintain compatibility with official platform features, especially those affecting basic usability and accessibility. The current situation represents a failure to meet this expectation. While implementing dark mode support does require development effort, the current accessibility issues are preventing users from effectively using existing functionality. This aligns with our standard definition of a bug - where existing features no longer work as intended for a subset of our users. I recommend we reclassify these issues as bugs with appropriate priority levels based on their severity and impact on user accessibility.

            Rajshri added a comment -

            ' ARJ—Dark theme' is out of scope for the 10.3 release and is being planned for a future release.

            The information about plans not supported is included in the next release notes for both JSM and JSW -  https://hello.atlassian.net/wiki/spaces/SDS/pages/4342215227/Jira+Service+Management+10.3.x+LTS+release+notes#Dark-theme-is-officially-here

            Just one last milestone left—we’re actively working on making the Plans view available in dark theme. Stay tuned!

            We have closed this bug since the feature is in progress.

            Rajshri added a comment - ' ARJ—Dark theme' is out of scope for the 10.3 release and is being planned for a future release. The information about plans not supported is included in the next release notes for both JSM and JSW -   https://hello.atlassian.net/wiki/spaces/SDS/pages/4342215227/Jira+Service+Management+10.3.x+LTS+release+notes#Dark-theme-is-officially-here Just one last milestone left—we’re actively working on making the Plans view available in dark theme. Stay tuned! We have closed this bug since the feature is in progress.

              427d436cf927 Rajshri
              rrosa@atlassian.com Rodrigo Rosa
              Affected customers:
              0 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: