Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-79172

Remote Link updates are not immediately reflected in remotelink database table

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 10.3.12
    • Application Links
    • None

      Issue Summary

      Renaming the Application link doesn't immediately reflect in the database, occurring only after loading the issue page.

      Steps to Reproduce

      1. Set up two Jira Instances, referred to as Jira A and Jira B.
      2. Create an Application Link:
      In Jira A, establish a new application link to Jira B, naming it "JiraA to JiraB."
      3. Add a Remote Link:
      In Jira A, create an issue (e.g., Issue-1) and add a remote link to an issue in Jira B. Ensure you select "JiraA to JiraB" as the server when creating the link.
      4. Verify the Application Name:
      Run the following SQL query to check the applicationname in the remotelink table:

      SELECT * FROM remotelink;
      

      Note that the applicationname column reflects "JiraA to JiraB."
      5. Rename the Application Link:
      Change the application link name in Jira A from "JiraA to JiraB" to "JiraC to JiraD."
      6. Run the SQL query again:

      SELECT * FROM remotelink;
      

      7. Observe that the applicationname still shows "JiraA to JiraB," indicating that it hasn't updated immediately.
      8. Check Issue History:
      Open Issue-1 in Jira A. You'll see that the history shows a remote link update under your username, with the update date set to the current date, which is incorrect.
      9. Final Verification:
      Reload the issue page in Jira A, then run the SQL query once more. The applicationname should now be updated to "JiraC to JiraD."

      Expected Results

      The change is immediately reflected in the database

      Actual Results

      The change only occurs when loading the issue page, resulting in a new entry being added to the issue history as if the change had occurred at the time of the issue page load.

      Workaround

      To avoid incorrect history entries and update dates, you can directly update the applicationname in the database.

      Ensure you take a full database backup before proceeding!
      Test the following SQL update thoroughly in a lower environment before applying it to production:

      -- Update the applink name 'JiraC to JiraD' and 'JiraA to JiraB' accordingly
      UPDATE remotelink SET applicationname = 'JiraC to JiraD' WHERE applicationname = 'JiraA to JiraB';
      

              Unassigned Unassigned
              6bebacf0c7e4 Aline Staudt
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: