This really is a shame. This request is now 11 years old. Flexible wording and being able to brand every communication from a system is critical for any organization using a service desk. If we were aware of this limitation when we made our choice, we would have chosen another product from another company. There is a difference between being a satisfied customer, and being stuck.
This issue has been open for 12 years. Atlassian obviously use JIRA internally, I imagine you use the plugin to make your product bearable? You should disable all the non-standard addins so you can see what a pain your software can be for everyone else.
Abomination!
This dumb comment utility has vastly superior text formatting and styling options than those provided in Confluence!
The ability to format text according to need and preference in a platform like Confluence requires no explanation — it is obvious to anyone who has ever used a word processor.
It is an urgent requirement that should have been met in the original release, not relegated to its longstanding neglected status.
Unbelievable.
+me
This is a joke, 3k+ votes on this yet no follow up. This is a highly asked feature and is a pain point for your customers. ATLASSIAN, DO YOU NOT CARE?
Maybe all the 3k that voted need to start writing an email a day to Nathan Sturgess, Product Manager, Jira Platform. Just like how Andy did in Shawshank Redemption when he wanted to get the Library built :)
For the love of our eyes, PLEASE MAKE THIS HAPPEN! I actively avoid doing Jira work at night because of the eye strain, which unfortunately is when it makes the most sense to update Jira issues after a day's work. Using third party client-side hacks is not an acceptable solution.
Thanks to the +1,000,000 people that continue using Jira’s Dark theme. We are now confident that we can close the highest voted request in Atlassian’s history.
We are still working on a few bits and bobs, but none of that is preventing the full use of the feature.
In January 2022, a group of people at Atlassian decided to migrate a 20 year old product comprised of thousands of screens and a mature Ecosystem. We didn’t take the task lightly and we are proud of the outcome.
Theming is transforming all Atlassian products: [Confluence has already confirmed its release|https://www.atlassian.com/wac/roadmap/cloud/confluence-dark-mode?search=dark&p=4d13a231-c0] and our [Data Center products|https://www.atlassian.com/wac/roadmap/data-center/dark-mode?p=0b79e81f-2b] too!
You can read more about this big milestone here: [https://www.atlassian.com/blog/announcements/the-story-of-dark-theme]
We highly appreciate your patience and for believing in us ❤️
Sincerely,
The Jira Dark theme team
Hey all, I have disappointing news for all of you. This work has been paused in order to focus on performance improvements and other accessibility initiatives. We still believe this is still highly important work and we understand the impact this is having on some of our customers. Unfortunately we do not have an estimate on when it will resume. This is a hard update to make as it comes after the 4 year anniversary of this ticket; nonetheless, we want to ensure that all of you are informed.
This change in direction has been made centrally in our Design System which will lead to improvements across many properties, but in the meantime it affects Jira’s ability to roll out dark mode directly. That doesn’t remove the sting of this for those of us who are passionate about dark mode, but know that the decision from our leaders was made with the customer in mind. When Design System has capacity to pick this up again, myself or whoever owns the work at the time will update all of you.
I think everyone understands there are workarounds, including browser extensions, but for some of us, we're not willing to open security holes like browser extensions for something as simple as a css dark mode ( which has been a thing for like 10+ years in web development ).
I'm a front-end engineer, so I know how easy it is to implement, it's literally just loading the correct style sheet based on a setting... it's so simple the only possible explanation for this ( over a year now? ) delay, would be red-tape type top-down management, endless design meetings, and feature creep...
The most ironic thing for me about this "dark theme feature request" is the inability of this company in particular to get it done, as they provide SaaS to basically help other companies get it done...lol
I too have rather enjoyed the recent spate of comments. Looks like I first commented on this issue in 2006. Wow. But I agree with Greg's last statement that Atlassian has paid far too much attention to the U.I. and not (some of) the functionality. U.I. is much sexier and more fun to do I'm sure. I still prefer the look and feel of version 3. While using the user interface editable group name as a key was a design mistake from over 10 years ago, I don't see it as a technically huge challenge to fix, much less challenging I think than some of the U.I. and marketplace changes I have seen in the past 12 years. I still rely heavily on a small handful of add-ons to do what should be in the core product.
I suspect there are people that think my comments add no value to this issue. That's not really true.
When I was first investigating using JIRA for my company, I would have very much liked to have seen negative comments in the manner I am leaving, that highlight that Atlassian DO NOT CARE about their userbase or fixing long-standing issues, and that instead they focus on changing UI elements.
These comments may not be relevant to YOU as someone who has been watching this (and other "suggestions") for a long time, but for brand new companies considering Atlassian products, they provide useful information about the character of the company.
Atlassian's products are the type that once you invest your company into using them, it can be quite difficult to switch away from. So the more information about the lack of support that Atlassian actually gives to their customers, the better people can make informed decisions about whether Atlassian products are right for them.
If you don't want "spam", then stop watching the ticket.
Hey Nathan, no rush, it's only been *SIXTEEN YEARS* since this was requested. At least Jira Server got this three years ago. But hey, keep telling people that feedback from your customers is really important while you're fiddling with shiny buttons and more white-space in the UI.
I agree with previous comments, don't put this only in Next-gen. We have disabled next-gen from day one because for us it only creates problems, it doesn't solve any.
@Ronald - now now, they have over 100 emojis you can choose from! You don't get it, software development teams don't need features, they need a way to express themselves emotionally. Atlassian is doing its best to make sure we can communicate our technical problems in a friend, fun, visual way. I especially like how my url route strings go from /api/route/: pk > /api/route/:Pk <-- Tongue out emoji in JIRA
See - that's the stuff they are focusing on, because it's important!
Seriously though - it's pretty outrageous that after 16 years no one thought the concept of differing priorities between projects wasn't core functionality to a product that aims to bring all "Teams" together into one platform. Sorry to say, but accounts teams don't normally have a "Showstopper" priority.
I'm speechless to even try and make a comment here... but c'mon, I can do this! Just breathe... breathe...
Ok, Nathan Sturges, Jira's Product Manager, has it ever occurred to you that Jira is only as successful as it has been simply because it actually allows customization and flexibility???
Some people want simple - and I understand why Atlassian wants to push for next-gen. I, however, as a Jira admin, don't give a flying crock about next-gen. I'm an admin for a large corporation and we want complexity! We want to design complex workflows and solutions because of the complexity of the business. And by the way, I don't want other people to manage most pf my projects! Next-gen is not our thing here!
That said, what do you do with tens of thousands of users that are on the same situation as my company???
Oh, I know! The answer is you just ignore them! And ignore a ticket created in 2004 with almost 5k votes!
This is absolutely stupid. The proof this is a big need is the fact that you actually have this feature in Jira Server! Yes, you can create priority schemes and define different priorities per project - which is something OBVIOUS (even thou it's obvious, I'll explain -
In your instance you might have projects that have a completely different approach - i.e., projects that are Service Management, others are business, others development, and so on. That said, I will most likely want to see priorities in a different way. For instance, for product support it might look something completely different that what it looks like for development - which is actually I use case I've seen for every single company I worked for/with in the last 20 years.
All that being said, your comment about simplifying is a non-sense. It might make sense for next-gen people, but what is actually the percentage of your users that are next-gen customers?
The decision to be complex and simple MUST be mine, as a user of this tool! Therefore, Atlassian's responsibility it to build a tool that allows for complex and simple. Not just try to amputate the legs that have take you this far!
That's my two cents - which I'll give to you for free today. You're welcome.
Figured I'd come back here for my annual check-in on this ignored request. This is no longer a feature comment section, it's a public forum for the discouraged & exasperated Jira admins/users that are fed up with Atlassian's MO of willful ignorance & screwing over their existing customers.
They're pushing simplicity for Cloud & leaving complexity/customization for DC.
All of the customers/organizations that naively migrated to Cloud (before discovering all of the gotchas & functionalities lost) will be migrating again to a better solution after Atlassian makes Jira Cloud the McDonalds/Walmart of issue tracking. They'll be eventually phasing out all remaining native complexity & customizations to further align with *every* Cloud "solution" scheme .... put anything/everything useful or connective behind additional PAYWALLS.
Turns out all the promises & hype of the Cloud was just a smokescreen for taking away all the controls from users, locking in subscription license revenues, pushing a bunch of hokey-pokey features that nobody asked for (emojis & team-managed projects??) all while conveniently ignoring practical & useful requests backed by thousands of votes & comments.
See ya'll here next year!
It's been a while since I've been this upset over a UI change, but this is right up there with the fiasco of the Microsoft Skype UI change that had people switch to competitors overnight.
*This change will be added to University textbooks as a case study of terrible UX design to be studied for the rest of time.*
I sincerely hope that this extremely ill-conceived ‘improvement’ will be rolled back asap. More importantly, *Atlassian should conduct an* *internal investigation into the decision-making process behind this update* — specifically the methods and criteria the responsible team used to assess the "positive" impact on the user experience.
I'd just like to point out that Atlassian have rolled out AI, which must have taken months, and which is frankly dangerous. I asked it several times to tell me what an acronym stood for. This acronym was known to me but not documented in our Confluence space. Over each request it MADE UP a different definition for the acronym, complete with explanation, and presented it as fact, with each definition explicitly not existing in our space. Cool.
The point being that Atlassian have spent considerable resource making something that doesn't work instead of adding basic, but essential, features such as are requested here.
My issue is also that some customers send 4 social media logos plus their company logo. Not only does that give me 5 attachments I have to delete one by one each time the customer replies, the Comments section gets really unruly with lots of scrolling past huge written out image links and logos blown up to fit the width of the comment field. It's like a tower of logos after every reply. If I clean up the comment, the customer will get notified (public) or I'll hide their comment from them in the portal (internal). Both is undesirable. Some customers switch between email and portal use. Overall 3 out of 5 come in via mail, and 2 of 5 via the portal.
This really is a shame. This request is now 11 years old. Flexible wording and being able to brand every communication from a system is critical for any organization using a service desk. If we were aware of this limitation when we made our choice, we would have chosen another product from another company. There is a difference between being a satisfied customer, and being stuck.
This issue has been open for 12 years. Atlassian obviously use JIRA internally, I imagine you use the plugin to make your product bearable? You should disable all the non-standard addins so you can see what a pain your software can be for everyone else.
Abomination! This dumb comment utility has vastly superior text formatting and styling options than those provided in Confluence! The ability to format text according to need and preference in a platform like Confluence requires no explanation — it is obvious to anyone who has ever used a word processor. It is an urgent requirement that should have been met in the original release, not relegated to its longstanding neglected status. Unbelievable.
+me This is a joke, 3k+ votes on this yet no follow up. This is a highly asked feature and is a pain point for your customers. ATLASSIAN, DO YOU NOT CARE? Maybe all the 3k that voted need to start writing an email a day to Nathan Sturgess, Product Manager, Jira Platform. Just like how Andy did in Shawshank Redemption when he wanted to get the Library built :)
It baffles me that this isn't available yet. Atlassian succeeds in so many areas, listening to customers is not one of them.
For the love of our eyes, PLEASE MAKE THIS HAPPEN! I actively avoid doing Jira work at night because of the eye strain, which unfortunately is when it makes the most sense to update Jira issues after a day's work. Using third party client-side hacks is not an acceptable solution.
Thanks to the +1,000,000 people that continue using Jira’s Dark theme. We are now confident that we can close the highest voted request in Atlassian’s history. We are still working on a few bits and bobs, but none of that is preventing the full use of the feature. In January 2022, a group of people at Atlassian decided to migrate a 20 year old product comprised of thousands of screens and a mature Ecosystem. We didn’t take the task lightly and we are proud of the outcome. Theming is transforming all Atlassian products: [Confluence has already confirmed its release|https://www.atlassian.com/wac/roadmap/cloud/confluence-dark-mode?search=dark&p=4d13a231-c0] and our [Data Center products|https://www.atlassian.com/wac/roadmap/data-center/dark-mode?p=0b79e81f-2b] too! You can read more about this big milestone here: [https://www.atlassian.com/blog/announcements/the-story-of-dark-theme] We highly appreciate your patience and for believing in us ❤️ Sincerely, The Jira Dark theme team
Hey all, I have disappointing news for all of you. This work has been paused in order to focus on performance improvements and other accessibility initiatives. We still believe this is still highly important work and we understand the impact this is having on some of our customers. Unfortunately we do not have an estimate on when it will resume. This is a hard update to make as it comes after the 4 year anniversary of this ticket; nonetheless, we want to ensure that all of you are informed. This change in direction has been made centrally in our Design System which will lead to improvements across many properties, but in the meantime it affects Jira’s ability to roll out dark mode directly. That doesn’t remove the sting of this for those of us who are passionate about dark mode, but know that the decision from our leaders was made with the customer in mind. When Design System has capacity to pick this up again, myself or whoever owns the work at the time will update all of you.
I think everyone understands there are workarounds, including browser extensions, but for some of us, we're not willing to open security holes like browser extensions for something as simple as a css dark mode ( which has been a thing for like 10+ years in web development ). I'm a front-end engineer, so I know how easy it is to implement, it's literally just loading the correct style sheet based on a setting... it's so simple the only possible explanation for this ( over a year now? ) delay, would be red-tape type top-down management, endless design meetings, and feature creep... The most ironic thing for me about this "dark theme feature request" is the inability of this company in particular to get it done, as they provide SaaS to basically help other companies get it done...lol
I too have rather enjoyed the recent spate of comments. Looks like I first commented on this issue in 2006. Wow. But I agree with Greg's last statement that Atlassian has paid far too much attention to the U.I. and not (some of) the functionality. U.I. is much sexier and more fun to do I'm sure. I still prefer the look and feel of version 3. While using the user interface editable group name as a key was a design mistake from over 10 years ago, I don't see it as a technically huge challenge to fix, much less challenging I think than some of the U.I. and marketplace changes I have seen in the past 12 years. I still rely heavily on a small handful of add-ons to do what should be in the core product.
I suspect there are people that think my comments add no value to this issue. That's not really true. When I was first investigating using JIRA for my company, I would have very much liked to have seen negative comments in the manner I am leaving, that highlight that Atlassian DO NOT CARE about their userbase or fixing long-standing issues, and that instead they focus on changing UI elements. These comments may not be relevant to YOU as someone who has been watching this (and other "suggestions") for a long time, but for brand new companies considering Atlassian products, they provide useful information about the character of the company. Atlassian's products are the type that once you invest your company into using them, it can be quite difficult to switch away from. So the more information about the lack of support that Atlassian actually gives to their customers, the better people can make informed decisions about whether Atlassian products are right for them. If you don't want "spam", then stop watching the ticket.
Hey Nathan, no rush, it's only been *SIXTEEN YEARS* since this was requested. At least Jira Server got this three years ago. But hey, keep telling people that feedback from your customers is really important while you're fiddling with shiny buttons and more white-space in the UI. I agree with previous comments, don't put this only in Next-gen. We have disabled next-gen from day one because for us it only creates problems, it doesn't solve any.
@Ronald - now now, they have over 100 emojis you can choose from! You don't get it, software development teams don't need features, they need a way to express themselves emotionally. Atlassian is doing its best to make sure we can communicate our technical problems in a friend, fun, visual way. I especially like how my url route strings go from /api/route/: pk > /api/route/:Pk <-- Tongue out emoji in JIRA See - that's the stuff they are focusing on, because it's important! Seriously though - it's pretty outrageous that after 16 years no one thought the concept of differing priorities between projects wasn't core functionality to a product that aims to bring all "Teams" together into one platform. Sorry to say, but accounts teams don't normally have a "Showstopper" priority.
I'm speechless to even try and make a comment here... but c'mon, I can do this! Just breathe... breathe... Ok, Nathan Sturges, Jira's Product Manager, has it ever occurred to you that Jira is only as successful as it has been simply because it actually allows customization and flexibility??? Some people want simple - and I understand why Atlassian wants to push for next-gen. I, however, as a Jira admin, don't give a flying crock about next-gen. I'm an admin for a large corporation and we want complexity! We want to design complex workflows and solutions because of the complexity of the business. And by the way, I don't want other people to manage most pf my projects! Next-gen is not our thing here! That said, what do you do with tens of thousands of users that are on the same situation as my company??? Oh, I know! The answer is you just ignore them! And ignore a ticket created in 2004 with almost 5k votes! This is absolutely stupid. The proof this is a big need is the fact that you actually have this feature in Jira Server! Yes, you can create priority schemes and define different priorities per project - which is something OBVIOUS (even thou it's obvious, I'll explain - In your instance you might have projects that have a completely different approach - i.e., projects that are Service Management, others are business, others development, and so on. That said, I will most likely want to see priorities in a different way. For instance, for product support it might look something completely different that what it looks like for development - which is actually I use case I've seen for every single company I worked for/with in the last 20 years. All that being said, your comment about simplifying is a non-sense. It might make sense for next-gen people, but what is actually the percentage of your users that are next-gen customers? The decision to be complex and simple MUST be mine, as a user of this tool! Therefore, Atlassian's responsibility it to build a tool that allows for complex and simple. Not just try to amputate the legs that have take you this far! That's my two cents - which I'll give to you for free today. You're welcome.
Figured I'd come back here for my annual check-in on this ignored request. This is no longer a feature comment section, it's a public forum for the discouraged & exasperated Jira admins/users that are fed up with Atlassian's MO of willful ignorance & screwing over their existing customers. They're pushing simplicity for Cloud & leaving complexity/customization for DC. All of the customers/organizations that naively migrated to Cloud (before discovering all of the gotchas & functionalities lost) will be migrating again to a better solution after Atlassian makes Jira Cloud the McDonalds/Walmart of issue tracking. They'll be eventually phasing out all remaining native complexity & customizations to further align with *every* Cloud "solution" scheme .... put anything/everything useful or connective behind additional PAYWALLS. Turns out all the promises & hype of the Cloud was just a smokescreen for taking away all the controls from users, locking in subscription license revenues, pushing a bunch of hokey-pokey features that nobody asked for (emojis & team-managed projects??) all while conveniently ignoring practical & useful requests backed by thousands of votes & comments. See ya'll here next year!
It's been a while since I've been this upset over a UI change, but this is right up there with the fiasco of the Microsoft Skype UI change that had people switch to competitors overnight. *This change will be added to University textbooks as a case study of terrible UX design to be studied for the rest of time.*
I sincerely hope that this extremely ill-conceived ‘improvement’ will be rolled back asap. More importantly, *Atlassian should conduct an* *internal investigation into the decision-making process behind this update* — specifically the methods and criteria the responsible team used to assess the "positive" impact on the user experience.
I'd just like to point out that Atlassian have rolled out AI, which must have taken months, and which is frankly dangerous. I asked it several times to tell me what an acronym stood for. This acronym was known to me but not documented in our Confluence space. Over each request it MADE UP a different definition for the acronym, complete with explanation, and presented it as fact, with each definition explicitly not existing in our space. Cool. The point being that Atlassian have spent considerable resource making something that doesn't work instead of adding basic, but essential, features such as are requested here.
My issue is also that some customers send 4 social media logos plus their company logo. Not only does that give me 5 attachments I have to delete one by one each time the customer replies, the Comments section gets really unruly with lots of scrolling past huge written out image links and logos blown up to fit the width of the comment field. It's like a tower of logos after every reply. If I clean up the comment, the customer will get notified (public) or I'll hide their comment from them in the portal (internal). Both is undesirable. Some customers switch between email and portal use. Overall 3 out of 5 come in via mail, and 2 of 5 via the portal.
only 17 years and counting since this was logged