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

Allow users to toggle automatic linking in Jira cloud for outlook addon

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 1.0
    • Jira Cloud for Outlook
    • None
    • Severity 3 - Minor

      Issue Summary

      Currently, the Jira cloud for outlook addon (installed in outlook itself), will attempt to link to any sort of Jira cloud issue if it detects a Jira cloud "key" format. Unfortunately, this means that certain date formats like:

      JUL-18

      For july 18th, end up being linked and cause issues when users attempt to highlight sentences or portions of messages for copying as it instead copies as a URL instead of just text.

      Allowing users to turn off the this sort of auto-link will improve usability. The semi-related FR for this involving smart linking doesn't resolve this unfortunately since this is an issue in text found within outlook instead of Jira

      This is reproducible on Data Center: (yes) / (no)

      Steps to Reproduce

      1. View any message in in outlook with Jira cloud for outlook installed with the date format of MONTH-DAY and you'll see that it attempts to auto link (i.e., JUL-18)

      Expected Results

      It should not be attempting to link for projects that don't exist within the user's instance and is a date.

      Actual Results

      Attempts to link regardless
      N/A

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [API-730] Allow users to toggle automatic linking in Jira cloud for outlook addon

            Renzo N. added a comment -

            I would've expected at least a workaround by now...

            Renzo N. added a comment - I would've expected at least a workaround by now...

            Tomas Kondelka_c added a comment -

            +1

            Tomas Kondelka_c added a comment - +1

            jason.back added a comment -

            Recommended solution:
            The addon would only display in the email if it found a related Jira ticket. If no related Jira ticket is found then display as normal text.

             

            Workable solution:

            Allow the user to enter a list of blacklisted prefixes that the addon never tried to find a related Jira ticket. 

            Example: HAZ, JAN

            HAZ-123456 - do not display

            JAN-12 - do not display

            TEST-123 - display

            This would not be ideal because the user would then need to enter a long list of prefixes that they don't want the addon to trigger on and would have to know all of the project keys within Jira.

            jason.back added a comment - Recommended solution: The addon would only display in the email if it found a related Jira ticket. If no related Jira ticket is found then display as normal text.   Workable solution: Allow the user to enter a list of blacklisted prefixes that the addon never tried to find a related Jira ticket.  Example: HAZ, JAN HAZ-123456 - do not display JAN-12 - do not display TEST-123 - display This would not be ideal because the user would then need to enter a long list of prefixes that they don't want the addon to trigger on and would have to know all of the project keys within Jira.

              mbamba@atlassian.com mbamba
              3176abc1c383 Hieuy Mac
              Affected customers:
              8 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated: