Issue Summary

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. Install GitLab 15.0.
      2. Connect Jira to GitLab 
      3. Wait 2 hours

      Expected Results

      The token refresh should take place in the background.

      Actual Results

      The token expires and cannot be refreshed without reestablishing the application link.  This will erase development details in other parts of Jira. 

      Workaround

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

      The only known workaround is to recreate the link with a full synch.  

            [JSWSERVER-21389] Jira session token with GitLab 15 times out after 2 hours

            I am facing the same issue with Jira cloud and self hosted gitlab

            Suraj Risal added a comment - I am facing the same issue with Jira cloud and self hosted gitlab

            I don't know if the issue is the token but I have the same issue with Jira 8.22.6 and Gitlab CE 15.9.2 

            When establishing the link everything works fine. After a while there are no updates anymore. The only way to fix it is to recreate the link.

            Oliver Lobisch added a comment - I don't know if the issue is the token but I have the same issue with Jira 8.22.6 and Gitlab CE 15.9.2  When establishing the link everything works fine. After a while there are no updates anymore. The only way to fix it is to recreate the link.

            Looks like it's curious patch

            Gonchik Tsymzhitov added a comment - Looks like it's curious patch

            Rusi Popov added a comment -

            Rusi Popov added a comment - The problem is reproduced and analyzed with JIRA 8.20.11 and GitLab 15.4.3 ee in https://jira.atlassian.com/browse/JSWSERVER-21243?focusedCommentId=3189438&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3189438

            Thanks for that fix

            Gonchik Tsymzhitov added a comment - Thanks for that fix

            Is the issue fixed in 8.20.11? Why is JSWSERVER-21417 still open (looks like a duplicate)?

            Caterina Trainito added a comment - Is the issue fixed in 8.20.11? Why is JSWSERVER-21417 still open (looks like a duplicate)?

            Hi,

            I'm also indeed interested in knowing if Jira cloud will be updated with the fix and when ?

            This is a blocker for us to upgrade our self-hosted gitlab instance to v15. (and i well noticed that DVCS connector won't work anymore with gitlab v16, letting me more time to anticipate this and hoping that gitlab app for Jira will also evolve until there).

            Thanks and regards,

            AUBERT Alexandre added a comment - Hi, I'm also indeed interested in knowing if Jira cloud will be updated with the fix and when ? This is a blocker for us to upgrade our self-hosted gitlab instance to v15. (and i well noticed that DVCS connector won't work anymore with gitlab v16, letting me more time to anticipate this and hoping that gitlab app for Jira will also evolve until there). Thanks and regards,

            This issue is happening on Jira Cloud as well. Will it be fixed for Jira Cloud too?

            Emily Chang added a comment - This issue is happening on Jira Cloud as well. Will it be fixed for Jira Cloud too?

              Unassigned Unassigned
              samann Sarah A
              Affected customers:
              9 This affects my team
              Watchers:
              34 Start watching this issue

                Created:
                Updated:
                Resolved: