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

Jira for Slack app does not unfurl issues when the issue key is posted by another bot/app

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • 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.

      Problem Definition

      • When using The Jira app for Slack (official) we are expecting that the Jira bot unfurl issues when a Jira issue key is mentioned.
      • However, when an issue key is posted by another App/bot, I can see that intentionally Jira bot is ignoring it and the issue key preview does not show up.
      • I'm aware that it was configured by design to ignore other bots as it was the source of some incidents in the past.

      Suggested Solution

      • Provide a feature to whitelist bots.
      • Provide a feature to read whitelisted bots messages and unfurl the issue key when posted.

      Why this is important

      • More user friendly.
      • less time consuming.
      • better user experience.

      Workaround

      • Manually type the issue key.

            [API-103] Jira for Slack app does not unfurl issues when the issue key is posted by another bot/app

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3217374 ] New: JAC Suggestion Workflow 3 [ 3588389 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Trevor Thompson (Inactive) made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Gathering Interest [ 11772 ] New: RESOLVED [ 5 ]
            Fares Abbes (Inactive) created issue -

              Unassigned Unassigned
              fabbes Fares Abbes (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: