• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Jira Cloud for Slack
    • None
    • 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.

      It would be great to have the ability of when the issue is commented in JIRA, the comment is added to the thread that was created with the issue (or in a single thread per issue), instead of being added as a new separated comment on Slack.

      Or to have the link of the thread added as an internal comment (or in another way) inside the ticket that was created. With this customers can send the last comment via Automation.

      This would be great for teams that work using Slack, as all issue data would be related to a single thread.

            [API-342] Jira issue comments in a single thread of Slack (per issue)

            +1

            +1

            Jatin Masiwal added a comment - +1

            +1

            +1

            Does Atlassian team use slack? Why is this extremely legitimate requirement held up here for 4 years... 

            Victor Zhou (ENG - BE - HK) added a comment - +1 Does Atlassian team use slack? Why is this extremely legitimate requirement held up here for 4 years... 

            Anthony added a comment -

            +1, please create this functionality.  We'd like to use Jira/Slack integration more but folks see it more like spam

            Anthony added a comment - +1, please create this functionality.  We'd like to use Jira/Slack integration more but folks see it more like spam

            Hi, this would be hugely useful for reducing Slack noise and making Jiras more useful, any idea when it will be implemented? Thanks

            Phil O'Malley added a comment - Hi, this would be hugely useful for reducing Slack noise and making Jiras more useful, any idea when it will be implemented? Thanks

            +1 appreciate sharing the last update for this 

            Bayan Hashem added a comment - +1 appreciate sharing the last update for this 

            This is what I need!!

            We have an automation in JSM that does the following:

            Issue wakes up as Open

            We send an email to the customer or we comment on the JSM Issue, this triggers a comment into the JSM Issue and transitions the Issue to "Waiting for Customer".

            Then Customer send us an email, or comments on the JSM Issue, this triggers a comment into the JSM Issue and transitions the Issue to "Waiting for Support".

            I want to add to the automation this smart value:

            Last Comment: | now.convertToTimeZone("Asia/Jerusalem").jqlDateTime IDT
            issue.comments.last.body

             

            but the last comment is huge and makes a mess in Slack main channel. 

             

            I want the comments to ramp up in the thread of the original slack message connected to the JSM Issue that triggered it.

             

            same thing for Jira Issues of course, if we have comments on our slack automations for Jira Issues.

             

            the full message from the automation is currently this:

            @channel
            <url|key> | issueType.name | status.name
            Summary:
            summary

            Last Comment: | now.convertToTimeZone("Asia/Jerusalem").jqlDateTime IDT
            issue.comments.last.body

             

            eilon_elphi added a comment - This is what I need!! We have an automation in JSM that does the following: Issue wakes up as Open We send an email to the customer or we comment on the JSM Issue, this triggers a comment into the JSM Issue and transitions the Issue to "Waiting for Customer". Then Customer send us an email, or comments on the JSM Issue, this triggers a comment into the JSM Issue and transitions the Issue to "Waiting for Support". I want to add to the automation this smart value: Last Comment: | now.convertToTimeZone("Asia/Jerusalem").jqlDateTime IDT issue.comments.last.body   but the last comment is huge and makes a mess in Slack main channel.    I want the comments to ramp up in the thread of the original slack message connected to the JSM Issue that triggered it.   same thing for Jira Issues of course, if we have comments on our slack automations for Jira Issues.   the full message from the automation is currently this: @channel < url | key > | issueType.name | status.name Summary: summary Last Comment: | now.convertToTimeZone("Asia/Jerusalem").jqlDateTime IDT issue.comments.last.body  

            Upvote +1

             

            Bhaumik Shrivastava added a comment - Upvote +1  

            so how does this get pushed? I'm interested.

            brandon.j.buller added a comment - so how does this get pushed? I'm interested.

            infra added a comment -

            +1

            infra added a comment - +1

            +1 please

            Jack Moorhouse added a comment - +1 please

            Hey, any news on this one?

            As it is configured today this integration is very spammy and it's hard to follow up on tickets: information are spread across the channel. 

            Organising everything related to a given ticket in a thread would be game changer 

             

             

            Madeleine Tahimi added a comment - Hey, any news on this one? As it is configured today this integration is very spammy and it's hard to follow up on tickets: information are spread across the channel.  Organising everything related to a given ticket in a thread would be game changer      

            Would be a great addition, please consider. 

            Elian Dutra added a comment - Would be a great addition, please consider. 

            b1airo added a comment -

            This, or something like it, would be very helpful for reducing channel "noise". One of Slack's greatest features is threading, it keeps conversation on a specific topic logically grouped while leaving the main channel free for new conversations to start (unlike e.g. Teams). Integrations that don't take advantage of this are clogging up our channels.

            Reminding people of proper threading etiquette is modern equivalent of telling people not to top-post in Usenet (https://www.idallen.com/topposting.html for anyone too young to get this reference).

            b1airo added a comment - This, or something like it, would be very helpful for reducing channel "noise". One of Slack's greatest features is threading, it keeps conversation on a specific topic logically grouped while leaving the main channel free for new conversations to start (unlike e.g. Teams). Integrations that don't take advantage of this are clogging up our channels. Reminding people of proper threading etiquette is modern equivalent of telling people not to top-post in Usenet ( https://www.idallen.com/topposting.html for anyone too young to get this reference).

            sinta added a comment -

            This functionality is also available via Zapier. Any idea if this feature will be available via the Jira Slack Integration?

            sinta added a comment - This functionality is also available via Zapier. Any idea if this feature will be available via the Jira Slack Integration?

            Looking forward to this. Right now, it's confusing for end users who will post within Slack thinking that they are also commenting on the Jira ticket. Most of our end users are very much "Slack first" and we'd like to encourage this behaviour for non-developers. Threaded comments will resolve this and prevent miscommunication and related slow downs as a result.

            Shaye Murray added a comment - Looking forward to this. Right now, it's confusing for end users who will post within Slack thinking that they are also commenting on the Jira ticket. Most of our end users are very much "Slack first" and we'd like to encourage this behaviour for non-developers. Threaded comments will resolve this and prevent miscommunication and related slow downs as a result.

            Please consider.  It's already available with the Halp integration so many just borrow their code?

            David Roberts added a comment - Please consider.  It's already available with the Halp integration so many just borrow their code?

            Same as API-118?

            leroy.kahn@zip.co added a comment - Same as API-118 ?

            Hello,

            It looks like the interest for that feature is increasing. Can we have an update on if this request please? Can this be taken into consideration please?

            Cheers.

            Michel Lieke added a comment - Hello, It looks like the interest for that feature is increasing. Can we have an update on if this request please? Can this be taken into consideration please? Cheers.

            Hello,

             

            Very interested in this feature. 

            Jordan Capola added a comment - Hello,   Very interested in this feature. 

            lienngo added a comment -

            I am also looking forward it too.

            lienngo added a comment - I am also looking forward it too.

            In my company too!!!

            Cristina Moriguchi added a comment - In my company too!!!

            This would have a tremendous impact on our company!
            thanks 

            Dotan Huberman added a comment - This would have a tremendous impact on our company! thanks 

            We need this functionality like oxygen. Are there any chances to deliver it?

            Artur Owczarek added a comment - We need this functionality like oxygen. Are there any chances to deliver it?

            We are looking for a similar solution. 

            When a task is done and there is a notification sent on slack about it, it would be amazing if such notification contains further info about the task such as the comments in a thread.

            Thank you, 

            Alfonso Villar added a comment - We are looking for a similar solution.  When a task is done and there is a notification sent on slack about it, it would be amazing if such notification contains further info about the task such as the comments in a thread. Thank you, 

            Michel Lieke added a comment - - edited

            Hello, 

             

            Hope you are well today.

            I would be very interested to know if the issue described below could be taken into consideration? Heading up the digital department in my company I will have to make efficient change on processes as soon as we can. One of them will be that feature. 

            Please feel free to let me know if you need anything from me.

             

            Cheers, 

            Mich

            Michel Lieke added a comment - - edited Hello,    Hope you are well today. I would be very interested to know if the issue described below could be taken into consideration? Heading up the digital department in my company I will have to make efficient change on processes as soon as we can. One of them will be that feature.  Please feel free to let me know if you need anything from me.   Cheers,  Mich

              Unassigned Unassigned
              mdossantos Matheus
              Votes:
              135 Vote for this issue
              Watchers:
              73 Start watching this issue

                Created:
                Updated: