• Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • 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.

      I'd like the ability to create a new Slack channel from within a Jira Service Desk (or Software) issue.  Specifically I'm hoping to automate this action based on the setting of a custom field.  For example, when a JSD issue's custom field, Severity, is set to Sev1 or Sev2, then create a new Slack channel whose name is that of the issue's key (e.g., SERVICE-13).  From that point forward, the Slack channel and the JSD issue should be linked with updates going bi-directionally.

            [API-224] Create Slack Channel from Jira Issue

            Hello - I've been trying to find a way to do what I think this issue is meaning to address?
            Being able to automatically generate a slack channel based on the project + issue type that is used when creating a ticket.

            Is this actively being worked on? Is it actively being tracked as a roadmap item?

            Charlotte Hamilton added a comment - Hello - I've been trying to find a way to do what I think this issue is meaning to address? Being able to automatically generate a slack channel based on the project + issue type that is used when creating a ticket. Is this actively being worked on? Is it actively being tracked as a roadmap item?
            Sebastian Thierer made changes -
            Link New: This issue was cloned as API-577 [ API-577 ]

            This is not a duplicate as pointed out above. This does not add the functionality to automatically create a Slack channel upon creation of a Jira issue.

            mike.wright added a comment - This is not a duplicate as pointed out above. This does not add the functionality to automatically create a Slack channel upon creation of a Jira issue.

            This ticket should be reopened because API-65 did not do this.

            Andy Markulis added a comment - This ticket should be reopened because API-65 did not do this.
            Daniel Eads made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Daniel Eads made changes -
            Link New: This issue duplicates API-65 [ API-65 ]

            Hi Paul,

            Thanks for your suggestion! I noted that this is essentially the same use-case as an existing feature request, API-65 - therefore I'm closing this suggestion out as a duplicate. Please take a second to Watch the other issue and add any details you think might be missing from your use-case as a comment.

            Thanks!
            Daniel | Atlassian Support

            Daniel Eads added a comment - Hi Paul, Thanks for your suggestion! I noted that this is essentially the same use-case as an existing feature request, API-65 - therefore I'm closing this suggestion out as a duplicate. Please take a second to Watch the other issue and add any details you think might be missing from your use-case as a comment. Thanks! Daniel | Atlassian Support
            Paul Benati created issue -

              Unassigned Unassigned
              8d276f158664 Paul Benati
              Votes:
              1 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: