Summary

      The default font color (when you select from the text color selection) is "red". See:

      But once another font color is chosen (other than red), you can no longer select red anymore. Clicking on red actually produced #d04437 instead:

      Steps to Reproduce

      1. Clear browser caches
      2. Login with a new user
      3. Either edit the description of an issue, or add a comment to an issue
      4. Highlight some text, and change its color to red via the text color selector. Notice that it is the correct color on the text now (color set to red)
      5. Highlight another block of text and change its color to blue.
      6. Now highlight another block of text and change its color to red again. Notice that it's the wrong color now (color set to #d04437 )

      Expected Results

      Color should be set back to "red".

      Actual Results

      Color is set to #d04437 , and it will be that color forever, in the text color selector no matter where you go (editing another issue, add a comment to another issue, etc. It will never go back to red unless you clear your browser caches and site data - including cookies)

      Workaround

      Clear all the browser caches and site data, including cookies. Otherwise, just manually change #d04437 to "red"

        1. d.png
          d.png
          16 kB
        2. red.png
          red.png
          16 kB

            [JRASERVER-63319] Text color changes from red to #d04437

            I've also just noticed the RED in palette and the actual Red in markup is different.So annoying!

             

            Celine Hau added a comment - I've also just noticed the RED in palette and the actual Red in markup is different. So annoying!  

            Atlassian Update – 22.07.2021

            Hi Everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.
            Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Thank you,
            Ewelina Fiedorowicz

            Ewelina Fiedorowicz added a comment - Atlassian Update – 22.07.2021 Hi Everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ewelina Fiedorowicz

              Unassigned Unassigned
              fsim Foo Sim (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: