[FE-6332] Remote events fail silently if Base URL does not match Application Link URL

Type: Bug
Resolution: Won't Fix
Priority: Low
Fix Version/s: None
Affects Version/s: 3.9.0
Component/s: None
Labels:

Symptom Severity:
Severity 3 - Minor
UIS:
22
Bug Fix Policy:
View Atlassian Server bug fix policy

If JIRA's Base URL does not match the URL used by AppLinks remote events are dropped silently.
JIRA publishes via REST the event capabilities it can handle with their corresponding URL. Said URL is created using the application's Base URL. When that URL does not match the AppLinks URL the event cannot be sent and the error is not logged.

This might result in delayed updates about development information in the JIRA development panel.

causes

JSWCLOUD-13889 Commits in FeCru/Stash takes a long time to be updated in JIRA when Display URL and Application URL is different

Closed

JSWSERVER-13889 Commits in FeCru/Stash takes a long time to be updated in JIRA when Display URL and Application URL is different

Closed

is cloned from

BSERV-7802 Remote events fail silently if Base URL does not match Application Link URL

Closed

is related to: FUSE-2967 Failed to load

mentioned in: Page Failed to load; Page Loading...; Page Loading...; Page Loading...

(3 mentioned in)

Form Name

SCS Team added a comment - 23/Feb/2016 9:44 AM

We are seeing this issue in our configuration. Any estimate on when this might be integrated?

SCS Team added a comment - 23/Feb/2016 9:44 AM We are seeing this issue in our configuration. Any estimate on when this might be integrated?

Lukasz Pater added a comment - 23/Jan/2016 10:44 AM

Seems the updated remote-events is now available, so we should consider integrating it. cc: pswiecicki

Lukasz Pater added a comment - 23/Jan/2016 10:44 AM Seems the updated remote-events is now available, so we should consider integrating it. cc: pswiecicki

Grzegorz Lewandowski added a comment - 12/Oct/2015 10:15 AM

I wasn't able to reproduce the behavior really, but FeCru is most likely affected also. Anyway I don't think we can do anything useful on our side, we should rather wait till resolution of FUSE-2967.

Grzegorz Lewandowski added a comment - 12/Oct/2015 10:15 AM I wasn't able to reproduce the behavior really, but FeCru is most likely affected also. Anyway I don't think we can do anything useful on our side, we should rather wait till resolution of FUSE-2967.

Piotr Swiecicki added a comment - 10/Sep/2015 9:20 AM

FeCru is most likely affected too

Piotr Swiecicki added a comment - 10/Sep/2015 9:20 AM FeCru is most likely affected too

Assignee:: Unassigned

Reporter:: Juan Palacios (Inactive)

Affected customers:: 2 This affects my team

Watchers:: 10 Start watching this issue

Created:: 10/Sep/2015 9:17 AM

Updated:: 14/Nov/2018 12:31 PM

Resolved:: 14/Nov/2018 12:31 PM

Details

Description

Attachments

Issue Links

Forms

Activity

Collapse comment: SCS Team added a comment - 23/Feb/2016 9:44 AM

Expand comment: SCS Team added a comment - 23/Feb/2016 9:44 AM

Collapse comment: Lukasz Pater added a comment - 23/Jan/2016 10:44 AM

Expand comment: Lukasz Pater added a comment - 23/Jan/2016 10:44 AM

Collapse comment: Grzegorz Lewandowski added a comment - 12/Oct/2015 10:15 AM

Expand comment: Grzegorz Lewandowski added a comment - 12/Oct/2015 10:15 AM

Collapse comment: Piotr Swiecicki added a comment - 10/Sep/2015 9:20 AM

Expand comment: Piotr Swiecicki added a comment - 10/Sep/2015 9:20 AM

People

Dates