Uploaded image for project: 'Atlassian Product Integrations'
  1. Atlassian Product Integrations
  2. API-342

Jira issue comments in a single thread of Slack (per issue)

XMLWordPrintable

    • 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)

            Jatin Masiwal added a comment -

            +1

            Jatin Masiwal added a comment - +1

            Kandula Chakradhar Reddy added a comment -

            +1

            Kandula Chakradhar Reddy added a comment - +1

            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... 

            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

            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

            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

            Bayan Hashem added a comment -

            +1 appreciate sharing the last update for this 

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

            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

             

            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  

            Bhaumik Shrivastava added a comment -

            Upvote +1

             

            Bhaumik Shrivastava added a comment - Upvote +1  

            brandon.j.buller added a comment -

            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

              Unassigned Unassigned
              mdossantos Matheus
              Votes:
              121 Vote for this issue
              Watchers:
              65 Start watching this issue

                Created:
                Updated: