Backbone receives error that project does not exist

Description

Steps to reproduce
There are no exact steps to reproduce the problem.

  1. Setup a synchronization - problem was detect on Jira Data Center but probably reproducible on a regular Jira Server instance as well

  2. Wait until sync user's session is expired

  3. Open a Backbone synchronization

Expected result
Backbone is automatically retrieving a new user session and shows the UI without errors (in case it's a synchronization without any conflicts/connection errors/etc.).

Actual result
Backbone receives an error that the project does not exist due to an expired cookie. It also shows errors in the UI that permissions etc. are missing.

Environment

None

implements changes caused by

Activity

Show:
Fixed

Details

Assignee

Reporter

Deployment

Data Center

Components

Fix versions

Affects versions

Priority

Backbone Issue Sync

Created September 11, 2020 at 8:04 AM
Updated February 15, 2023 at 4:41 PM
Resolved September 11, 2020 at 8:04 AM