Backbone receives error that project does not exist
Description
Steps to reproduce There are no exact steps to reproduce the problem.
Setup a synchronization - problem was detect on Jira Data Center but probably reproducible on a regular Jira Server instance as well
Wait until sync user's session is expired
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.
Steps to reproduce
There are no exact steps to reproduce the problem.
Setup a synchronization - problem was detect on Jira Data Center but probably reproducible on a regular Jira Server instance as well
Wait until sync user's session is expired
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.