Jira Service Management knowledge base and REST API functionalities breaks if viewport and servicedesk sequences mismatch

Issue Summary

Jira Service Management has two sets of tables: AO_54307E_VIEWPORT and AO_54307E_SERVICEDESK.
These tables each have their own IDs and Service Management expects them to be the same. If for some reason they fall out of sync, some features will break.

• Opening a KB (knowledge base) article from the portal works, but from within the request summary doesn't (error of non-existing article shows up)
• The portal has one ID when navigating through the browser, but another — invalid — ID when requested through REST API.

Steps to Reproduce

1. Integrate JSM with Confluence through App Links
2. Alter AO_54307E_VIEWPORT_ID_seq or AO_54307E_SERVICEDESK_ID_seq so they no longer have the same next values
3. Create a Service Management project with a Confluence KB space
4. Create an article in confluence with the title "HOW TO ACCESS"
5. On the JSM portal, search for "how to access" and click on the article that shows up. It'll open
6. Go back and select a request from the new project
7. On the summary, type "how to access" and click on the article that shows up. I'll say the article doesn't exist.

Expected Results

1. JSM shouldn't allow the sequences to become out of sync

Actual Results

1. JSM has a heavy dependency on the sequences being in sync but there's no FK on the database enforcing it.
2. REST API starts producing wrong results
3. Confluence KB integration doesn't work when queried from the request creation form
   1. When checking the portal ID of the request creation form in the URL, we can see that the Portal ID is correct:
      
   2. However, when clicking on the KB article URL, we are redirected to a page showing the following error, which is due to the fact that the incorrect Portal ID is used in the KB article URL

      The service project you are trying to view does not exist
      

      

   3. If the KB article URL was properly built, it should be using the same portal ID as the one in the request form URL, and the KB should be displayed properly
      

Workaround

No workaround available. To fix this, we must update the sequences so they become synced again and update the ID on AO_54307E_VIEWPORT and its dependencies to match the AO_54307E_SERVICEDESK IDs.

The KB article Knowledge Base articles fail to open from the request form in Jira Service Management provides extra details on this fix.