Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-67971

Application Links health check displays warning for any external application links

XMLWordPrintable

      Update - Sep 25th 2018

      This ticket is resolved as the issue is now being tracked at https://ecosystem.atlassian.net/browse/ATST-916. Please watch that ticket for further updates.

      Original Description

      Steps to Reproduce

      Create an application link to an external source

      Expected Results

      Health check warnings would not appear on login.

      Actual Results

      Admin users receive alerts in Support Tools that there's a problem with Application Links. In the Health Check page, users will see

      One of your application links is reporting "Link to external third party".

      Notes

      There isn't anything inherently alarming about linking to external sources. The link in health check states "How can I resolve this", but this is misleading since there is nothing that needs to be resolved.

      Workaround

      No current workaround.

          Form Name

            [JRASERVER-67971] Application Links health check displays warning for any external application links

            Steve Allen added a comment -

            FYI: I am seeing this issue:
            Upgraded Jira from 7.1.4 to 7.12.3 & Confluence 5.9.9 to 6.12.2. Upgrade via a migrate.

            Steve Allen added a comment - FYI: I am seeing this issue: Upgraded Jira from 7.1.4 to 7.12.3 & Confluence 5.9.9 to 6.12.2. Upgrade via a migrate.

            Tom Davies added a comment -

            https://ecosystem.atlassian.net/browse/ATST-916

            Tom Davies added a comment - https://ecosystem.atlassian.net/browse/ATST-916

            Tom Davies added a comment -

            Tracked as https://ecosystem.atlassian.net/browse/ATST-916

            Tom Davies added a comment - Tracked as https://ecosystem.atlassian.net/browse/ATST-916

            Jan-Olof Degerbalkan added a comment -

            Upgraded Jira from 7.3.3 to 7.12.1 and Confluence from 6.2.2 to 6.11.1 and having the same behavior.

             

            Jan-Olof Degerbalkan added a comment - Upgraded Jira from 7.3.3 to 7.12.1 and Confluence from 6.2.2 to 6.11.1 and having the same behavior.  

            William Deshaies added a comment -

            v7.12.1 still having the issue

            William Deshaies added a comment - v7.12.1 still having the issue

            Hitendra Chauhan added a comment -

            v7.11.2 is having same behavior

            Hitendra Chauhan added a comment - v7.11.2 is having same behavior

            Shaun Farrugia added a comment -

            Same Behavior on Jira v7.11.2 in combination with Confluence 6.10.2

            Shaun Farrugia added a comment - Same Behavior on Jira v7.11.2 in combination with Confluence 6.10.2

            Manuel Bähnisch added a comment -

            Seeing the same behaviour after upgrading to Jira 7.12.1 in combination with Confluence 6.4.2 and 6.8.2.

            Manuel Bähnisch added a comment - Seeing the same behaviour after upgrading to Jira 7.12.1 in combination with Confluence 6.4.2 and 6.8.2.

            Mike Bianca added a comment -

            Also seeing this in Jira Server v7.10.1 

            Mike Bianca added a comment - Also seeing this in Jira Server v7.10.1 

            Larry Brock {Praecipio Consulting} added a comment -

            Also affects Jira v7.6.7 - "Enterprise Release".  Please add to affected versions.

            Larry Brock {Praecipio Consulting} added a comment - Also affects Jira v7.6.7 - "Enterprise Release".  Please add to affected versions.

              Unassigned Unassigned
              sseaver Shaun S
              Affected customers:
              182 This affects my team
              Watchers:
              157 Start watching this issue

                Created:
                Updated:
                Resolved: