Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-3406

Threaded / nested Comments / give the ability to reply to a comment

    • 3,773
    • 95
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Atlassian Update: 1st Feb 2025

      Hi all,

      I'm a Product Manager on Jira and part of the team working on building out threaded comments and we wanted to share an update with you all.

      This has been one of the longest running and highly requested JAC tickets from you all - thank you for being super patient with us to resolve this. Building threaded comments is a table stakes feature so that teams can have meaningful discussions in Jira. It is unfortunately not a trivial amount of effort to add threaded comments in Jira, which is part of the reason why it has taken so long to prioritise this effort.

      As some of you have noticed, we have recently been trialling a version of threaded comments. As a result, we now have a path towards adding threaded comments in Jira.

      I’m excited to share that we will be launching threaded comments early H2 FY25! In order to achieve this, we will need to temporarily roll back the recently shipped experience.

      What this means if you used the rolled back experience:

      There is no data loss. Your comments and associated data have not been affected.
      Until we roll threaded comments again, messages that were represented as a thread, will be temporarily flattened.
      Once we roll threaded comments out again, all previous threaded comments will be shown as threads again.
      It isn't ideal to temporarily flatten threads, however after evaluating all the trade-offs, this is the difficult decision we needed to make in order to deliver the best possible overall experience as quickly as possible.

      We can’t wait to finally roll threaded comments out for you all. Thank you all for your feedback - our product teams have been closely following your feedback from this ticket, community and support. Please continue to follow along on this ticket for updates as we start to roll threaded comments out.

      Tushar

      Product Manager, Jira

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Atlassian Update: 29th January 2024

      Hey everyone,

      Thank you very much for taking the time to participate in this issue and sharing your feature request with us. Your input is greatly appreciated, and we understand the effort and dedication it takes to provide us with your thoughts and ideas.

      We have considered this request, and we regret to inform you that we will not build the threaded/nested comments feature in Jira for the foreseeable future. We understand that this may be disappointing news, but we want to assure you that we take all customer feedback seriously. In the meantime, please continue to document your use cases, vote on, and share this ticket. This will help us to understand and prioritise this issue in the future.

      Instead, we want to share a possible workaround that can be used:

      • Use this Atlassian Marketplace App: Threaded Comments for Jira will provide the functionality for threaded/nested comments, allowing your team to respond directly to comments.

      Thank you for your patience and understanding.

      Kind regards,
      Lucy Zhu
      Product Management Team, JIRA

      Atlassian Update: 3rd April 2017

      Hi all,

      Again, thank you for participating in this issue, either by voting, commented or just watching. We highly value your feedback in all forms, and through suggestions in jira.atlassian.com is not different. We use this channel often to learn the best we can with how customers use JIRA and how we can continue to improve the experience for as many users as possible.

      While this is currently not on our roadmap in the next 12 months, we do hope to address this in the future, in a similar way to how Confluence does it today.

      Thank you for your patience and understanding. Please don't hesitate to contact me if you have any questions.

      Regards,
      Kerrod Williams
      Kerrod (dot) Williams (at) atlassian (dot) com
      Product Manager, JIRA

      Original request description

      Instead of having just a simple linear comment tree, how about being able to have an (optional) threaded view where replies to comments and replies to replies could be seen as such.

      The option to allow threaded comments, linear comments or even comments at all could be on an issue by issue basis as well as having project / global defaults which you could fall back on (if unselected).

            [JRACLOUD-3406] Threaded / nested Comments / give the ability to reply to a comment

            Pinned comments

            Pinned by Dylan

            Tushar Bhatia added a comment - - edited

            Hi all,

            I'm a Product Manager on Jira and part of the team working on building out threaded comments and we wanted to share an update with you all.

            This has been one of the longest running and highly requested JAC tickets from you all - thank you for being super patient with us to resolve this. Building threaded comments is a table stakes feature so that teams can have meaningful discussions in Jira. It is unfortunately not a trivial amount of effort to add threaded comments in Jira, which is part of the reason why it has taken so long to prioritise this effort.

            As some of you have noticed, we have recently been trialling a version of threaded comments. As a result, we now have a path towards adding threaded comments in Jira.

            I’m excited to share that we will be launching threaded comments early H2 FY25! In order to achieve this, we will need to temporarily roll back the recently shipped experience.

            What this means if you used the rolled back experience:

            • There is no data loss. Your comments and associated data have not been affected.
            • Until we roll threaded comments again, messages that were represented as a thread, will be temporarily flattened.
            • Once we roll threaded comments out again, all previous threaded comments will be shown as threads again.

            It isn't ideal to temporarily flatten threads, however after evaluating all the trade-offs, this is the difficult decision we needed to make in order to deliver the best possible overall experience as quickly as possible. 

            We can’t wait to finally roll threaded comments out for you all. Thank you all for your feedback - our product teams have been closely following your feedback from this ticket, community and support. Please continue to follow along on this ticket for updates as we start to roll threaded comments out.

            Tushar

            Product Manager, Jira

            Tushar Bhatia added a comment - - edited Hi all, I'm a Product Manager on Jira and part of the team working on building out threaded comments and we wanted to share an update with you all. This has been one of the longest running and highly requested JAC tickets from you all - thank you for being super patient with us to resolve this. Building threaded comments is a table stakes feature so that teams can have meaningful discussions in Jira. It is unfortunately not a trivial amount of effort to add threaded comments in Jira, which is part of the reason why it has taken so long to prioritise this effort. As some of you have noticed, we have recently been trialling a version of threaded comments. As a result, we now have a path towards adding threaded comments in Jira. I’m excited to share that we will be launching threaded comments early H2 FY25! In order to achieve this, we will need to temporarily roll back the recently shipped experience. What this means if you used the rolled back experience: There is no data loss. Your comments and associated data have not been affected. Until we roll threaded comments again, messages that were represented as a thread, will be temporarily flattened. Once we roll threaded comments out again, all previous threaded comments will be shown as threads again. It isn't ideal to temporarily flatten threads, however after evaluating all the trade-offs, this is the difficult decision we needed to make in order to deliver the best possible overall experience as quickly as possible.  We can’t wait to finally roll threaded comments out for you all. Thank you all for your feedback - our product teams have been closely following your feedback from this ticket, community and support. Please continue to follow along on this ticket for updates as we start to roll threaded comments out. Tushar Product Manager, Jira

            All comments

            Julien,

            Send a support request to votazz and I will organise a discount promo code for your use

            Peter

            Peter Muldoon added a comment - Julien, Send a support request to votazz and I will organise a discount promo code for your use Peter

            Hi Peter,

            Don't get me wrong, I personally think you're doing a great job with this add-on.
            But I cannot get a buy in from IT or management because the price does no justify the value this add-on brings.
            We have about 100 users and growing. When I request a yearly budget of 1800USD for threaded comments, I'm getting laughed at.

            Cheers.

            Julien.

            Julien Béchade added a comment - Hi Peter, Don't get me wrong, I personally think you're doing a great job with this add-on. But I cannot get a buy in from IT or management because the price does no justify the value this add-on brings. We have about 100 users and growing. When I request a yearly budget of 1800USD for threaded comments, I'm getting laughed at. Cheers. Julien.

            Well, it's been a little over half a year since I made my comment, and I guess I got your explanation as to why this feature won't be implemented. Very shameful, and I'm wondering how this behavior matches your core values (specially the bull related one). 

            But it's not all bad! it's nice to see so many people who also care the usability of the products they use! so I thank (almost) everyone in this comment section for sharing your feedback with the world! Do know your efforts are appreciated by some.

            Cheers!

            Jose Ricardo Monegro Quezada added a comment - - edited Well, it's been a little over half a year since I made my comment, and I guess I got your explanation as to why this feature won't be implemented. Very shameful, and I'm wondering how this behavior matches your core values  (specially the bull related one).  But it's not all bad! it's nice to see so many people who also care the usability of the products they use! so I thank (almost) everyone in this comment section for sharing your feedback with the world! Do know your efforts are appreciated by some. Cheers!

            Hi Julien,

            We appreciate your comments and feedback
            We acknowledge that Votazz Threaded Comments is the number 1 feature requested by users  
            We accept that it does not offer everything native comments do
            This is why we welcome your suggestions as to how we may improve the app and make it work more effectively for you & your team
            We have scheduled a new release of Threaded Comments for Cloud for next week 1st May, and Threaded Comments for Data Centre by mid-May

            Peter Muldoon added a comment - Hi Julien, We appreciate your comments and feedback We acknowledge that Votazz Threaded Comments is the number 1 feature requested by users   We accept that it does not offer everything native comments do This is why we welcome your suggestions as to how we may improve the app and make it work more effectively for you & your team We have scheduled a new release of Threaded Comments for Cloud for next week 1st May, and Threaded Comments for Data Centre by mid-May

            Hi,

            Threaded comments is the number 1 feature requested by our users as it becomes hard to keep track of cross discussions when a lot of people are involved in an issue. The alternative you're proposing is very pricey for what it is and, the fact that it does not offer everything native comments do, is very confusing to end users. A shame this is not considered for the near future.

            Julien Béchade added a comment - Hi, Threaded comments is the number 1 feature requested by our users as it becomes hard to keep track of cross discussions when a lot of people are involved in an issue. The alternative you're proposing is very pricey for what it is and, the fact that it does not offer everything native comments do, is very confusing to end users. A shame this is not considered for the near future.

            Hi Zaz,

            Thanks for the feedback regards :-

            • You can't add attachments to comments, even images (!!!!!!)
            • You also can't add reactions, but that's minor.

            We are aware of these limitations, but unfortunately it is beyond our control

            See below:-

            Atlassian Response - 1st April 2024

            Following up on the inability to handle images & other non-test media in Threaded Comments Cloud, we got another reply from Anna at Atlassian saying she's struggling to get any answers from the Atlassian product team. 

            Our fear is that it's just not possible and the lack of answers from Atlassian seems to confirm this.

            Peter Muldoon added a comment - Hi Zaz, Thanks for the feedback regards :- You can't add attachments to comments, even images (!!!!!!) You also can't add reactions, but that's minor. We are aware of these limitations, but unfortunately it is beyond our control See below:- Atlassian Response - 1st April 2024 Following up on the inability to handle images & other non-test media in Threaded Comments Cloud, we got another reply from Anna at Atlassian saying she's struggling to get any answers from the Atlassian product team.  Our fear is that it's just not possible and the lack of answers from Atlassian seems to confirm this.

            Zaz Harris added a comment - - edited

            I just checked out the suggested add-on and it is a non-starter for several reasons:

            • You have to go to a Threaded Comments tab – 95% of people will never do this
            • You can't add attachments to comments, even images (!!!!!!)

            You also can't add reactions, but that's minor. After finding these two problems I didn't bother to check it out further.

            It is incredible that this is still not addressed and is easily one of the feature gaps mentioned to me most frequently as an administrator. Do better.

            Zaz Harris added a comment - - edited I just checked out the suggested add-on and it is a non-starter for several reasons: You have to go to a Threaded Comments tab – 95% of people will never do this You can't add attachments to comments, even images (!!!!!!) You also can't add reactions, but that's minor. After finding these two problems I didn't bother to check it out further. It is incredible that this is still not addressed and is easily one of the feature gaps mentioned to me most frequently as an administrator. Do better.

            Thanks Rohit,

            I have paseed your suggestion over to our dev team to investigate and implement, as appropriate

            Regards

            Peter, votazz Support Team

            Peter Muldoon added a comment - Thanks Rohit, I have paseed your suggestion over to our dev team to investigate and implement, as appropriate Regards Peter, votazz Support Team

            Come on guys. It's such a pain to know who has replied to which issue in the single email thread. How could you not implement this simple and very important feature ? 

            Rohit Choudhary added a comment - Come on guys. It's such a pain to know who has replied to which issue in the single email thread. How could you not implement this simple and very important feature ? 

            53fe6159a219 added a comment - 08/Mar/2024 11:06 AM
            We should celebrate!
            20 years of ignorance... Or being ignored....

            Only one more year and the issue will be legally (in the U.S.) allowed to go to a bar and drink its sorrows away about not being implemented

            mark.risman added a comment - 53fe6159a219  added a comment - 08/Mar/2024 11:06 AM We should celebrate! 20 years of ignorance... Or being ignored.... Only one more year and the issue will be legally (in the U.S.) allowed to go to a bar and drink its sorrows away about not being implemented

            We should celebrate!
            20 years of ignorance... Or being ignored....

            Marcelo Aguisky added a comment - We should celebrate! 20 years of ignorance... Or being ignored....

            Next week it's going to be 20 years! 🎉🎉🎉🎉

            Jakub Wagner added a comment - Next week it's going to be 20 years! 🎉🎉🎉🎉

            Atlassian you cannot just ignore such a popular request that easily, this is not how things work and definitely not how you should care about your customers. Just look at this ticket history, just look at what other tools offer, just look at how shamelessly you ask us to pay for a 3rd party plugin for a feature that should have been built in from the beginning. Not ashamed, really?

            You will not get rid of this request by ignoring it. This HAS to be implemented. It works in Confluence. I really start to believe the royalties you get from 3rd party vendors offering this feature is the only thing motivating you not to do it.

            Eric Dantec added a comment - Atlassian you cannot just ignore such a popular request that easily, this is not how things work and definitely not how you should care about your customers. Just look at this ticket history, just look at what other tools offer, just look at how shamelessly you ask us to pay for a 3rd party plugin for a feature that should have been built in from the beginning. Not ashamed, really? You will not get rid of this request by ignoring it. This HAS to be implemented. It works in Confluence. I really start to believe the royalties you get from 3rd party vendors offering this feature is the only thing motivating you not to do it.

            jeremyn added a comment -

            Interesting how an hour before Atlassian gives an update that they aren't going to make this obvious feature happen a person from the vendor they suggest creates and edits a post pushing their tool....

            Makes me wonder if "Vendor lobbied for us to not take away their revenue stream" is a resolution status in the backend of this ticket.

            jeremyn added a comment - Interesting how an hour before Atlassian gives an update that they aren't going to make this obvious feature happen a person from the vendor they suggest creates and edits a post pushing their tool.... Makes me wonder if "Vendor lobbied for us to not take away their revenue stream" is a resolution status in the backend of this ticket.

            Victor added a comment -

            Can we please re-open JRACLOUD-6412 so at least we get a reply button?

            Victor added a comment - Can we please re-open JRACLOUD-6412 so at least we get a reply button?

            Quite disappointing, Jira promotes management of development but in order to manage it we need to make finding information easier than what it is and trying to match a comment to a string of another comment without it being nested is virtually impossible, try this, in Outlook  turn conversation settings on and off.

            When it's on finding information is easy, the context of a reply makes sense because we all multitask, without context, to get context takes time, which is inefficient.

             

            Imagine texting 20 of your friends and each reply is a single message, you have no idea what each of the 20 is responding to, so you ask more questions, and get more answers, now you have a sea of responses but no idea what it is responding to.

             

            Turn conversation settings on and you can multitask more effectively in your work day, why is this? Because of the context it provides, your platform do not offer this so it doesn't do what it intends to do.

             

            Developers are complaining that they are spending to much time talking offline, and then not capturing the information, and as result can not be supported by someone other than the one who had the conversation, so not very AGILE now are we?

             

            You promote yourselves as AGILE, but it is not.

            Emile Steenkamp added a comment - Quite disappointing, Jira promotes management of development but in order to manage it we need to make finding information easier than what it is and trying to match a comment to a string of another comment without it being nested is virtually impossible, try this, in Outlook  turn conversation settings on and off. When it's on finding information is easy, the context of a reply makes sense because we all multitask, without context, to get context takes time, which is inefficient.   Imagine texting 20 of your friends and each reply is a single message, you have no idea what each of the 20 is responding to, so you ask more questions, and get more answers, now you have a sea of responses but no idea what it is responding to.   Turn conversation settings on and you can multitask more effectively in your work day, why is this? Because of the context it provides, your platform do not offer this so it doesn't do what it intends to do.   Developers are complaining that they are spending to much time talking offline, and then not capturing the information, and as result can not be supported by someone other than the one who had the conversation, so not very AGILE now are we?   You promote yourselves as AGILE, but it is not.

            Frustrating that you are withholding basic functionality and forcing us to buy a plugin

            Gregg Reaves added a comment - Frustrating that you are withholding basic functionality and forcing us to buy a plugin

            Dane Bostick added a comment - - edited

            It's crazy that this is the 6th most upvoted feature, which has been open since 2004...TWENTY YEARS...why did it take 20 years to tell us this is not going to be a feature? Very disappointed. Almost every alternative I've looked at has this feature. Hell, even Confluence has this feature.

            I have a feeling that the reason we won't have this feature is because Atlassian cares more about having developers in its marketplace than having satisfied customers. 

            Dane Bostick added a comment - - edited It's crazy that this is the 6th most upvoted feature, which has been open since 2004...TWENTY YEARS...why did it take 20 years to tell us this is not going to be a feature? Very disappointed. Almost every alternative I've looked at has this feature. Hell, even Confluence has this feature. I have a feeling that the reason we won't have this feature is because Atlassian cares more about having developers in its marketplace than having satisfied customers. 

            Craig Lang added a comment -

            I would reply to the comment that states they will not be implementing this feature with a negative reply...  but, alas, I cannot directly.  Because, oh yeah, no threaded comments.

            Craig Lang added a comment - I would reply to the comment that states they will not be implementing this feature with a negative reply...  but, alas, I cannot directly.  Because, oh yeah, no threaded comments.

            Peter Muldoon added a comment - - edited

            There are 130,000 + users of  Threaded Comments for Jira

            The app is available on Cloud & Data Centre 

            Check it out here:-  https://marketplace.atlassian.com/apps/1212145

            We release a new version every alternate month, and welcome your suggestions

             

            Peter Muldoon added a comment - - edited There are 130,000 + users of   Threaded Comments for Jira The app is available on Cloud & Data Centre   Check it out here:-   https://marketplace.atlassian.com/apps/1212145 We release a new version every alternate month, and welcome your suggestions  

            Hi everyone,

            Just wanted to drop a quick note about our gadget, IssueGlance Gadget for Jira (https://marketplace.atlassian.com/apps/1233213/issueglance-gadget-for-jira?tab=overview&hosting=cloud). Along with showing the last comment and recent activity on your dashboard, you can also quickly reply to comments and include the previous message as a block quote. 

            Best regards,
            Edouard @Buildmyapp Labs

            Buildmyapp.cloud added a comment - Hi everyone, Just wanted to drop a quick note about our gadget, IssueGlance Gadget for Jira ( https://marketplace.atlassian.com/apps/1233213/issueglance-gadget-for-jira?tab=overview&hosting=cloud ). Along with showing the last comment and recent activity on your dashboard, you can also quickly reply to comments and include the previous message as a block quote.  Best regards, Edouard @Buildmyapp Labs

            Katie added a comment -

            Comment threads are pretty standard now, I was really surprised when we started using Jira recently that this is not an available function.

            Katie added a comment - Comment threads are pretty standard now, I was really surprised when we started using Jira recently that this is not an available function.

            Ashwini Kumar added a comment - - edited

            Redmine has this feature since ages, I don't think this is such a big feature to wait so long. Considering there is already a feature to add emojis on a comment.

            Ashwini Kumar added a comment - - edited Redmine has this feature since ages, I don't think this is such a big feature to wait so long. Considering there is already a feature to add emojis on a comment.

            Atlassian Update: 3rd April 2017
            Hi all,

            Again, thank you for participating in this issue, either by voting, commented or just watching. We highly value your feedback in all forms, and through suggestions in jira.atlassian.com is not different. We use this channel often to learn the best we can with how customers use JIRA and how we can continue to improve the experience for as many users as possible.

            While this is currently not on our roadmap in the next 12 months, we do hope to address this in the future, in a similar way to how Confluence does it today.

             

            There are 1400+ upvotes on this issue, and countless comments. Why would this not be taken care of 19 years after the original request?  Was this update in 2017 just a lie?

             

             

            Harmony Hames added a comment - Atlassian Update: 3rd April 2017 Hi all, Again, thank you for participating in this issue, either by voting, commented or just watching. We highly value your feedback in all forms, and through suggestions in jira.atlassian.com is not different. We use this channel often to learn the best we can with how customers use JIRA and how we can continue to improve the experience for as many users as possible. While this is currently not on our roadmap in the next 12 months, we do hope to address this in the future, in a similar way to how Confluence does it today.   There are 1400+ upvotes on this issue, and countless comments. Why would this not be taken care of  19 years after the original request?   Was this update in 2017 just a lie?    

            Sorely missing this feature!

            Srđan Matijević added a comment - Sorely missing this feature!

            I ask myself, if there is any possibility to receive a feedback on this from Jira Support. Last update was made in 2017 telling that it's not planned for 2018

            Isabelle Burk added a comment - I ask myself, if there is any possibility to receive a feedback on this from Jira Support. Last update was made in 2017 telling that it's not planned for 2018

            Back again. I've just had to respond to a very long-running and tangled thread in a ticket. We're responding to each other like boomer lawyers do in email chains by saying stuff like "Please see my comments in red", and then another person commenting in purple... etc. 

            Ouch  

            Novan Sachrudi added a comment - Back again. I've just had to respond to a very long-running and tangled thread in a ticket. We're responding to each other like boomer lawyers do in email chains by saying stuff like "Please see my comments in red", and then another person commenting in purple... etc.  Ouch  

            Jeff Boon added a comment -

            Threaded commenting is an essential function in today's digital era! My team has expressed frustration over the challenge of keeping track of comments effectively, underscoring the fundamental need for threaded discussions.

            Jeff Boon added a comment - Threaded commenting is an essential function in today's digital era! My team has expressed frustration over the challenge of keeping track of comments effectively, underscoring the fundamental need for threaded discussions.

            Please consider this request. It's possible in Confluence so why not Jira issues? It would be so valuble to reply to a comment, especialy when the comment history is long and complicated.

            Sandra Axelsdottir added a comment - Please consider this request . It's possible in Confluence so why not Jira issues? It would be so valuble to reply to a comment, especialy when the comment history is long and complicated.

            I don't have an account but does anyone here have Twitter (or is Threads being used enough?) and can take it there, where it would get more publicity? Not sure that if I make one just for that, an account with 0 history would be even considered.

            Marcus Ebner added a comment - I don't have an account but does anyone here have Twitter (or is Threads being used enough?) and can take it there, where it would get more publicity? Not sure that if I make one just for that, an account with 0 history would be even considered.

            I just wanted to come by and let you guys know I have a brother who will be taking a drivers license exam next year, and is close to graduating form college.

            He was born a few months after this request was made.

            Nobody is asking for fancy features, we just want to be able to reply to comments. And I'm sure 16 years of tech debt or whatever might be a lot to go through, but I think it's pretty safe to say it isn't an insurmountable task for a company your size, and at this point I'm wondering if this is a deliberate design decision on your part, on which case I'd love to see an explanation for it, assuming there's any.

            Either way, if you have any feedback/comments to send my way, just make sure to repl- excuse me, tag me in here.

            Cheers

            Jose Ricardo Monegro Quezada added a comment - - edited I just wanted to come by and let you guys know I have a brother who will be taking a drivers license exam next year, and is close to graduating form college. He was born a few months after this request was made. Nobody is asking for fancy features, we just want to be able to reply to comments. And I'm sure 16 years of tech debt or whatever might be a lot to go through, but I think it's pretty safe to say it isn't an insurmountable task for a company your size, and at this point I'm wondering if this is a deliberate design decision on your part, on which case I'd love to see an explanation for it, assuming there's any. Either way, if you have any feedback/comments to send my way, just make sure to repl- excuse me, tag me in here. Cheers

            Tony added a comment -

            Tony added a comment - Even just the ability to reply to a comment like in MS Teams chats would be helpful. https://support.microsoft.com/en-us/office/reply-to-a-specific-message-in-chat-in-microsoft-teams-940c614c-4f07-41d4-850b-90f11da8329b  

            De Lorenzi Giorgio added a comment - - edited

            It's embarrassing that a paid platform doesn't have a so standard feature that a lot of software/platforms/forums/... have for free and also here we can read your update of 6 years ago in which you stated that this feature is already there in Confluence.... 6 years ago!

            De Lorenzi Giorgio added a comment - - edited It's embarrassing that a paid platform doesn't have a so standard feature that a lot of software/platforms/forums/... have for free and also here we can read your update of 6 years ago in which you stated that this feature is already there in Confluence.... 6 years ago!

            Iain Alexander added a comment - - edited

            I don't have a need for threaded external comments, only internal ones. Often we have agents leaving comments just replying to each other with "thanks" or "understood" and having these in a thread would save endless scrolling in long running tickets. (emoji are fine at times, but sometimes actual words are more precise)

            Personally, I think they might be annoying or hard to track if external comments are also threaded.

             

            Additionally: was this really raised in 2004? 

            Iain Alexander added a comment - - edited I don't have a need for threaded external comments, only internal ones. Often we have agents leaving comments just replying to each other with "thanks" or "understood" and having these in a thread would save endless scrolling in long running tickets. (emoji are fine at times, but sometimes actual words are more precise) Personally, I think they might be annoying or hard to track if external comments are also threaded.   Additionally: was this really raised in 2004? 

            We are in 2023 and the simplest feature of replying to a single comment is not possible? And this for a paid product? Shame on you.

            arne_schipper added a comment - We are in 2023 and the simplest feature of replying to a single comment is not possible? And this for a paid product? Shame on you.

            Pythonic added a comment -

            I cannot understand why this issue still existed but fixed, after creating it almost 20 years ago! 

            This shouldn't be a bug in technique, and must to be a bug of humanity from Atlassian.

            The cons of corrent linear layout are:

            1. You cann't see which comment is related to another one.
            2. When I add a comment, if the page is too long, I cann't see the orignal comment which I want to reply. I need to see it while editing if it contains many text.

            Pythonic added a comment - I cannot understand why this issue still existed but fixed, after creating it almost 20 years ago!  This shouldn't be a bug in technique, and must to be a bug of humanity from Atlassian. The cons of corrent linear layout are: You cann't see which comment is related to another one. When I add a comment, if the page is too long, I cann't see the orignal comment which I want to reply. I need to see it while editing if it contains many text.

            Yaz Vohra added a comment -

            This should be a must-have in Jira.   It has already been implemented in Atlas and lots of other tools as suggested by many.   Adding my sincere request for Atlassian to consider these cries for this feature and actually deliver. 

            Yaz Vohra added a comment - This should be a must-have in Jira.   It has already been implemented in Atlas and lots of other tools as suggested by many.   Adding my sincere request for Atlassian to consider these cries for this feature and actually deliver. 

            Afsal T A added a comment -

            Threaded comments with a comment ID reference is a necessary feature in such project management tools. That will help us to ensure the reply comments should address the corresponding main comment etc. In the Jira Server version, we internally developed some workaround to manage that it worked well for last few years. Now as we need to move to Cloud, that kind of workaround seems very difficult to implement, so we strongly demand an immediate attention to resolve the threaded comment request ion the Jira cloud plat form. I don't think it's hard to implement on Atlassian side as the similar feature is there in Confluence comments section.

             

            Afsal T A added a comment - Threaded comments with a comment ID reference is a necessary feature in such project management tools. That will help us to ensure the reply comments should address the corresponding main comment etc. In the Jira Server version, we internally developed some workaround to manage that it worked well for last few years. Now as we need to move to Cloud, that kind of workaround seems very difficult to implement, so we strongly demand an immediate attention to resolve the threaded comment request ion the Jira cloud plat form. I don't think it's hard to implement on Atlassian side as the similar feature is there in Confluence comments section.  

            It's embarrassing that in 2023 the feature is not only missing but the request is also being ignored. It's a standard feature for many ticket-management solutions since it has proven its value, and it's absolutely needed here as well. 

            Snezhana Petrova added a comment - It's embarrassing that in 2023 the feature is not only missing but the request is also being ignored. It's a standard feature for many ticket-management solutions since it has proven its value, and it's absolutely needed here as well. 

            Yes! This is a must-have for Jira Cloud, very disappointing that this hasn't been implemented and we're considering switching away just because of it!

            Ally Mitchell added a comment - Yes! This is a must-have for Jira Cloud, very disappointing that this hasn't been implemented and we're considering switching away just because of it!

            Jakub Wagner added a comment - - edited

            Atlassian! It's 2023 already.

            This is so embarrassing that there is no update for 6 years.

            Jakub Wagner added a comment - - edited Atlassian! It's 2023 already. This is so embarrassing that there is no update for 6 years.

            It's really disheartening that there has not been a single update from the Atlassian team on this. If there is a good reason why this cannot be implemented, just let us know! We have enough capacity to understand (if there is a technical reason for why this can't be implemented), and empathy (in case your team chooses to prioritize other important requests). A lot of us using Jira, after all, have to make these calls every day. 

            But to ignore so many cries for action is unacceptable. To mark this issue as "gathering interest" when there isn't a single Jira user who would not find this helpful, is shameful. To carry on without acknowledging the issue and making your paying customers feel simply heard, is disgraceful. 

             

            Aria Marta Kornas added a comment - It's really disheartening that there has not been a single update from the Atlassian team on this. If there is a good reason why this cannot be implemented, just let us know! We have enough capacity to understand (if there is a technical reason for why this can't be implemented), and empathy (in case your team chooses to prioritize other important requests). A lot of us using Jira, after all, have to make these calls every day.  But to ignore so many cries for action is unacceptable. To mark this issue as "gathering interest" when there isn't a single Jira user who would not find this helpful, is shameful. To carry on without acknowledging the issue and making your paying customers feel simply heard, is disgraceful.   

            Victor added a comment -

            Our issue has a "gathering interest" badge! Perhaps if we get all friends to comment on it we'll get it to the attention of our Atlassian overlords?

            Victor added a comment - Our issue has a "gathering interest" badge! Perhaps if we get all friends to comment on it we'll get it to the attention of our Atlassian overlords?

            @Atlassian people are paying for products, would be nice to have some feedback.

            • When will this be implemented?
            • If we want to exchange lot of information in the tickets, it can be a mess without the threads.

            Erki Tammik added a comment - @Atlassian people are paying for products, would be nice to have some feedback. When will this be implemented? If we want to exchange lot of information in the tickets, it can be a mess without the threads.

            Chris added a comment -

            20 years of "gathering interest" and still not implemented. This is one of the many reasons that my team keep pushing to leave Jira and probably one that prevents people from signing up.

            This cannot be that hard to implement. Just get it done already!!

            Chris added a comment - 20 years of "gathering interest" and still not implemented. This is one of the many reasons that my team keep pushing to leave Jira and probably one that prevents people from signing up. This cannot be that hard to implement. Just get it done already!!

            It's been almost 20 years since this issue has been created and it is still not implemented?!

            David Liebeherr added a comment - It's been almost 20 years since this issue has been created and it is still not implemented?!

            Yes hurry up and fix this. 

            Ben Van Walbeek added a comment - Yes hurry up and fix this. 

            +1

            Kim added a comment -

            +1. This feature would be very helpful

            Kim added a comment - +1. This feature would be very helpful

            Would love to see this feature returned in a future release! It saves so much time

            Justin Jackson added a comment - Would love to see this feature returned in a future release! It saves so much time

            Jason Rowe added a comment -

            +1 on the reply feature in tickets.

            Jason Rowe added a comment - +1 on the reply feature in tickets.

            Please implement! We lose productivity and efficiency by not having the reply feature. Thank you. 

            Miranda Goins added a comment - Please implement! We lose productivity and efficiency by not having the reply feature. Thank you. 

            Adding my comment to the many others saying that this basic functionality would be very useful for us.

            Marcus Ebner added a comment - Adding my comment to the many others saying that this basic functionality would be very useful for us.

            It's not even on your roadmap?   This should have been a core req for comments.  Today comments require a user to copy a comment to a new one and post the replay under it. 

            John Wilkerson added a comment - It's not even on your roadmap?   This should have been a core req for comments.  Today comments require a user to copy a comment to a new one and post the replay under it. 

            Please implement sooner!

            Kyle Simpson added a comment - Please implement sooner!

            YES!!!

            Helene Haderer added a comment - YES!!!

            Quentin added a comment -

            Again this morning I found one of my collegue posting a high quality comment on Jira and asking for the cooperation of a couple people. It would be really helpul to be able for them to share their opinion in a thread and to upvote the whole comment so that it is brought to every concerned parties

            Quentin added a comment - Again this morning I found one of my collegue posting a high quality comment on Jira and asking for the cooperation of a couple people. It would be really helpul to be able for them to share their opinion in a thread and to upvote the whole comment so that it is brought to every concerned parties

            +1. This would be very helpful.

            Josh Lambert added a comment - +1. This would be very helpful.

            yes, please!

            Julian Stöttinger added a comment - yes, please!

            Hi, please implement this useful feature. It will improve the readability of the comment stream

            Domenico Gambin added a comment - Hi, please implement this useful feature. It will improve the readability of the comment stream

            Ganga Nair added a comment -

            That would be great. Make it little more easier for the users.

            Ganga Nair added a comment - That would be great. Make it little more easier for the users.

            Threaded comments and replies would add huge value for Jira customers! Trello implemented this feature as a Power-Up back in 2021, see https://trello.com/power-ups/61782018054e2f19837ace09/threaded-comments-for-trello 

            Brendan Dowling added a comment - Threaded comments and replies would add huge value for Jira customers! Trello implemented this feature as a Power-Up back in 2021, see https://trello.com/power-ups/61782018054e2f19837ace09/threaded-comments-for-trello  

            This would be valuable, please do add.

            VAL.IVANIUK added a comment - This would be valuable, please do add.

            this would be awesome!

            Dennis Serkov added a comment - this would be awesome!

            Hi,

            Please implement this basic functionality

            Gregg Reaves added a comment - Hi, Please implement this basic functionality

            this would be great!

            Ben Weinberg added a comment - this would be great!

            This is a need where I am, implement asap. Thanks. 

            Ben Van Walbeek added a comment - This is a need where I am, implement asap. Thanks. 

            This should be basic functionality. And it should not be difficult to implement. The reply link could initiate a new comment with the original comment paragraph quoted.  Can anyone at Jira not see the usefulness of this?   You are replying to a specific comment, and it can be otherwise difficult to tell which comment your reply is referencing.  Comments often contain communication between multiple people.  Most web based forum software has provided something like this for 20 years.

            David Whiteman added a comment - This should be basic functionality. And it should not be difficult to implement. The reply link could initiate a new comment with the original comment paragraph quoted.  Can anyone at Jira not see the usefulness of this?   You are replying to a specific comment, and it can be otherwise difficult to tell which comment your reply is referencing.  Comments often contain communication between multiple people.  Most web based forum software has provided something like this for 20 years.

            eirens added a comment -

            I tried for five minutes straight and I couldn't imagine it. Sorry, @spenser.

            eirens added a comment - I tried for five minutes straight and I couldn't imagine it. Sorry, @spenser.

            Imagine it being 2023 and not having threaded comments.

            Spenser Coke added a comment - Imagine it being 2023 and not having threaded comments.

            Tzirel Shaffren added a comment - - edited

            Somebody just added a label to this Jira (check the history tab). I don't see any way that I (as a watcher) can edit the label field, so I'm guessing it's someone from Atlassian. Does this mean that there is actually someone at Atlassian who is aware of this Jira? Maybe that's a good sign?

            Tzirel Shaffren added a comment - - edited Somebody just added a label to this Jira (check the history tab). I don't see any way that I (as a watcher) can edit the label field, so I'm guessing it's someone from Atlassian. Does this mean that there is actually someone at Atlassian who is aware of this Jira? Maybe that's a good sign?

            we are working cross disiplines and threaded comments would really help us to be organized

            Lars-Harald Båtnes added a comment - we are working cross disiplines and threaded comments would really help us to be organized

            When, when, when will this be implemented ?

            I'm a big Jira fan, but I hate using comments because of this.

             

            David Burgess added a comment - When, when, when will this be implemented ? I'm a big Jira fan, but I hate using comments because of this.  

            This is very important, please add

            Simon Hostettler (SHOS) added a comment - This is very important, please add

            Such a simple feature

            Niek van Gogh added a comment - Such a simple feature

            Jira how can you not have this

            Niek van Gogh added a comment - Jira how can you not have this

            This is very important, please add

            Cristina Ripoll added a comment - This is very important, please add

            This is very important, please add

            Zahra Fakhri added a comment - This is very important, please add

            This is like the most important thing for me. I am surprised that such a basic thing is missing in JIRA.

            madhur13490 added a comment - This is like the most important thing for me. I am surprised that such a basic thing is missing in JIRA.

            AFAIK, the lack of the Threaded Comments feature is the one most inconvenient deficiency in JIRA. It's also maddeningly annoying (sic!) because users hit this problem every single day, for years on end... and – worse yet – they harbor desperate hopes of it being fixed (it's really a fix, not an improvement! - as this feature is implemented virtually everywhere else nowadays) eventually.

            I understand that JIRA is trying to be everything for everybody... but it looks that the JIRA development lately has been over-emphasizing high-flying Project Management related stuff over the "low-level" communications/discussions. Please throw a bone (this particular bone) to the poor developers and their team leads too!

            Denis Vakatov added a comment - AFAIK, the lack of the Threaded Comments feature is the one most inconvenient deficiency in JIRA. It's also maddeningly annoying (sic!) because users hit this problem every single day, for years on end... and – worse yet – they harbor desperate hopes of it being fixed (it's really a fix, not an improvement! - as this feature is implemented virtually everywhere else nowadays) eventually. I understand that JIRA is trying to be everything for everybody... but it looks that the JIRA development lately has been over-emphasizing high-flying Project Management related stuff over the "low-level" communications/discussions. Please throw a bone ( this particular bone) to the poor developers and their team leads too!

            Trevor Fell added a comment - - edited

            This ticket was created in 2004 - almost 20 years ago - I think it's safe to conclude that Atlassian intends to keep this functionality as a feature, not a bug.

            Perhaps it is meant to drive users to Confluence which (inexplicably) has threaded comments. Either way, its disappointing that this won't be addressed.

            Trevor Fell added a comment - - edited This ticket was created in 2004 - almost 20 years ago - I think it's safe to conclude that Atlassian intends to keep this functionality as a feature, not a bug. Perhaps it is meant to drive users to Confluence which (inexplicably) has threaded comments. Either way, its disappointing that this won't be addressed.

            Aria Marta Kornas added a comment - - edited

            This is so silly it makes me wanna cry. The comment section can have dozens of comments in it and it's impossible to distinguish who is replying to whom. It's a huge waste of my time to sift through the comments and play a detective to determine what is going on. You're wasting my time and time is money. Money is pizza. Pizza is life. 

            I want Jira to be my source of truth regarding any issue my team is working on. People quit, go on vacation, are sick, or just unavailable and so I have been putting in a lot of effort to encourage my team to bring in all the side conversations (from slack, emails, zoom meetings, etc) into Jira for better tracking. So that anyone can go into the system and know exactly what is going on. However, Jira sucks at helping us organize our thoughts and responses. At the pace you are going at (with your last response being from 2017) I am going to die of brain aneurysm from having to deal with this silliness. Come on Atlassian. It's almost 2023. Stop taking lame functionality tips from Outlook and start developing a product we all love to use. 

            Aria Marta Kornas added a comment - - edited This is so silly it makes me wanna cry. The comment section can have dozens of comments in it and it's impossible to distinguish who is replying to whom. It's a huge waste of my time to sift through the comments and play a detective to determine what is going on. You're wasting my time and time is money. Money is pizza. Pizza is life.  I want Jira to be my source of truth regarding any issue my team is working on. People quit, go on vacation, are sick, or just unavailable and so I have been putting in a lot of effort to encourage my team to bring in all the side conversations (from slack, emails, zoom meetings, etc) into Jira for better tracking. So that anyone can go into the system and know exactly what is going on. However, Jira sucks at helping us organize our thoughts and responses. At the pace you are going at (with your last response being from 2017) I am going to die of brain aneurysm from having to deal with this silliness. Come on Atlassian. It's almost 2023. Stop taking lame functionality tips from Outlook and start developing a product we all love to use. 

            Hello Atlassian it's almost 2023. 🔝

            Jakub Wagner added a comment - Hello Atlassian it's almost 2023. 🔝

            This functionality would be extremely useful!

            For now, I do this instead: 

            I start my comments with "Replying to [first words of comment I'm replying to]. 

            And I make the whole brackets portion a link of the original comment.

            Pavlina Drakou added a comment - This functionality would be extremely useful! For now, I do this instead:  I start my comments with "Replying to [first words of comment I'm replying to] .   And I make the whole brackets portion a link of the original comment.

            It's such a shame, it is forcing us to leave the product and have discussions elsewhere. Really disappointed.

            Niek van Gogh added a comment - It's such a shame, it is forcing us to leave the product and have discussions elsewhere. Really disappointed.

            Charles added a comment -

            Really surprised this hasn't been implemented yet - keeps the comment section so much cleaner and more readable with expandable thread options.

            Charles added a comment - Really surprised this hasn't been implemented yet - keeps the comment section so much cleaner and more readable with expandable thread options.

            Abigail A added a comment -

            This issue forces me out of Atlassian products and into their competition to have a clear conversation. 

            Abigail A added a comment - This issue forces me out of Atlassian products and into their competition to have a clear conversation. 

            Company migrated to Jira recently from TargetProcess.  A win in many respects, but having no threaded comments is a real let down. 

            It takes so much more time trying to gather which comment is being responded to, especially if stakeholders are involved in various streams and provides input to various teams.

            I didn't want to derail a very clear, unbroken chain of comms so I considered screenshotting a comment I was tagged in and responding to the original commenter via Slack with the screenshot for reference 

            Novan Sachrudi added a comment - Company migrated to Jira recently from TargetProcess.  A win in many respects, but having no threaded comments is a real let down.  It takes so much more time trying to gather which comment is being responded to, especially if stakeholders are involved in various streams and provides input to various teams. I didn't want to derail a very clear, unbroken chain of comms so I considered screenshotting a comment I was tagged in and responding to the original commenter via Slack with the screenshot for reference 

            I feel like anyone who is a cloud user, that uses Jira to actually manage work (especially with remote teams), just doesn't know how to complain that this feature isn't available. If they did this feature would already be implemented. 

            Charlie Roberts added a comment - I feel like anyone who is a cloud user, that uses Jira to actually manage work (especially with remote teams), just doesn't know how to complain that this feature isn't available. If they did this feature would already be implemented. 

            How is it possible in 2022 that this is not implemented yet?

            Trevor Fell added a comment - How is it possible in 2022 that this is not implemented yet?

            +1

            Andrey Donits added a comment - +1

            This is a really desirable feature for any team who cooperates on requirements and the work itself.

            There are options for this on the market place, but none offer the following very desirable detail:

            A very useful addition I recommend for this feature is to be able to mark a comment thread resolved (Gitlab do this to great effect!), so that people don't have to go diving down a rabbit hole of comments, only to find the whole thread is already "done".

            Marc Binns added a comment - This is a really desirable feature for any team who cooperates on requirements and the work itself. There  are options for this on the market place, but none offer the following very desirable detail: A very useful addition I recommend for this feature is to be able to mark a comment thread resolved ( Gitlab do this to great effect !), so that people don't have to go diving down a rabbit hole of comments, only to find the whole thread is already "done".

            This feature is so convenient

            Sophia Chen added a comment - This feature is so convenient

            +1

            Jakub Matolín added a comment - +1

            Please Jira, without this feature, having discussions on issues is just so cumbersome 

            Michael Jauk added a comment - Please Jira, without this feature, having discussions on issues is just so cumbersome 

            a.baturin added a comment -

            We really want to see it this year

            a.baturin added a comment - We really want to see it this year

            gbarzu added a comment -

            This would be a very useful feature. 

            gbarzu added a comment - This would be a very useful feature. 

            Rejul S added a comment -

            This is a very useful and common feature. I can't understand why this Issue hasnt been implemented yet. Please get to this @Atlassian

            Rejul S added a comment - This is a very useful and common feature. I can't understand why this Issue hasnt been implemented yet. Please get to this @Atlassian

            Nadia added a comment -

            Please we need this option in the cloud available as well. 

            Nadia added a comment - Please we need this option in the cloud available as well. 

            Atlassian! It's year 2022.  

            Jakub Wagner added a comment - Atlassian! It's year 2022.  

            Andy Wu added a comment -

            +1 on this request!

            Andy Wu added a comment - +1 on this request!

              9aed6e7b8ed1 Shikhar Pahadia
              dhardiker Dan Hardiker
              Votes:
              1718 Vote for this issue
              Watchers:
              633 Start watching this issue

                Created:
                Updated: