• Icon: Bug Bug
    • Resolution: Not a bug
    • Icon: Medium Medium
    • None
    • 5.1
    • None

      The correct behaviour until 5.0.3 was that the text was shown as entered.

      Now confluence just converts everything into uppercase which is not what users expect and want!

            [CONFSERVER-28822] Status macro converts all text into UPPERcase

            To override the capitalisation

            It doesn't work, because Confluence puts uppercase in the output HTML, regardles the case entered in the macro properties.

            Cezariusz Marek added a comment - To override the capitalisation It doesn't work, because Confluence puts uppercase in the output HTML, regardles the case entered in the macro properties.

            Hi Markus

            Unfortunately the fix described here won't work in Confluence as the content you add to the status lozenge is converted to upper case. Changes to the style of this content will, unfortunately, have not effect.

            As stated above, at the current time we have no plans to change the design of the lozenges.

            Regards

            Steve Haffenden (Inactive) added a comment - Hi Markus Unfortunately the fix described here won't work in Confluence as the content you add to the status lozenge is converted to upper case. Changes to the style of this content will, unfortunately, have not effect. As stated above, at the current time we have no plans to change the design of the lozenges. Regards

            Hello Henry,

            thanks for your explanation.
            Well, different companies have different usecases...so WE would like to have the option (which was already in older version).

            But ok, if we could tweak our instance would be ok as well!
            I tried your css-snippet...but how to get it working?
            I've added it to both global as well space stylesheet areas..but the status macro behaves the same.
            Maybe there's already doc available? if yes please provide a link.

            Thanks /Markus

            Markus Lepper added a comment - Hello Henry, thanks for your explanation. Well, different companies have different usecases...so WE would like to have the option (which was already in older version). But ok, if we could tweak our instance would be ok as well! I tried your css-snippet...but how to get it working? I've added it to both global as well space stylesheet areas..but the status macro behaves the same. Maybe there's already doc available? if yes please provide a link. Thanks /Markus

            Thank you for your feedback Markus.

            There are no plans to implement a keep case option for status macros. Status macros have been designed to communicate a simple status such as "In progress", "Done", rather than complex strings such as those in your example.

            The status macro follows a pattern we have across our products for status lozenges that aims to make lozenges stand out in the UI and be instantly recognisable whilst being compact enough to be used inline in a wide variety of contexts.

            To achieve this, we explored several variations and found that the current implementation worked the best. We found using lower case resulted in status macros being less legible and recognisable.

            To override the capitalisation, you could add this CSS to the custom stylesheet globally or in specific spaces:

            .status-macro.aui-lozenge {
                text-transform: inherit;
            }
            

            Thanks,
            Henry
            Design Lead, Confluence

            Hank (Inactive) added a comment - Thank you for your feedback Markus. There are no plans to implement a keep case option for status macros. Status macros have been designed to communicate a simple status such as "In progress", "Done", rather than complex strings such as those in your example. The status macro follows a pattern we have across our products for status lozenges that aims to make lozenges stand out in the UI and be instantly recognisable whilst being compact enough to be used inline in a wide variety of contexts. To achieve this, we explored several variations and found that the current implementation worked the best. We found using lower case resulted in status macros being less legible and recognisable. To override the capitalisation, you could add this CSS to the custom stylesheet globally or in specific spaces: .status-macro.aui-lozenge { text-transform: inherit; } Thanks, Henry Design Lead, Confluence

            Any comment by Atlassian's UI Design team?

            In addition the code on https://confluence.atlassian.com/display/CONF35/Writing+the+Status+User+Macro could be updated to give the new design of Status boxes. I would create my own Status-macro and allow Camelcasing...

            TNX /Markus

            Markus Lepper added a comment - Any comment by Atlassian's UI Design team? In addition the code on https://confluence.atlassian.com/display/CONF35/Writing+the+Status+User+Macro could be updated to give the new design of Status boxes. I would create my own Status-macro and allow Camelcasing... TNX /Markus

            Hello Renan,

            we use quite intensively the status macro showing relations/status/dependencies between different software modules.
            As we use quite long camel-case-labels the all-upper-case does render the status macro unusable for us. (See attached screenshot)

            => So I would very much like to see at least an config-option to allow same cases as typed; like "[ ] Keep case".

            Thanks for your consideration
            Markus

            Markus Lepper added a comment - Hello Renan, we use quite intensively the status macro showing relations/status/dependencies between different software modules. As we use quite long camel-case-labels the all-upper-case does render the status macro unusable for us. (See attached screenshot) => So I would very much like to see at least an config-option to allow same cases as typed; like " [ ] Keep case ". Thanks for your consideration Markus

            Hi Markus,

            For 5.1 and newer versions the text inside the status lozenge is made uppercased by design.

            Would you clarify to what use cases you are applying the macro? Would you also provide screen shots so that our team can valuate the visual impact?

            Cheers,
            Renan

            Renan Battaglin added a comment - Hi Markus, For 5.1 and newer versions the text inside the status lozenge is made uppercased by design. Would you clarify to what use cases you are applying the macro? Would you also provide screen shots so that our team can valuate the visual impact? Cheers, Renan

              shaffenden Steve Haffenden (Inactive)
              0925485d2514 Markus Lepper
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: