Jira Connect handle installation updates
According to this Atlassian developer community post Jira Connect install events can also serve as an update. For example if a user changes the site URL, GitLab will receive an installed event containing a new baseUrl
.
Current behavior
Jira lifecycle events are used to create or destroy JiraConnectInstallation
s. But we also receive installed
events when an installation already exists. Currently, we just ignore those events (app/controllers/jira_connect/events_controller.rb:10
).
Expected behavior
The existing installation should be updated with the contents of the event parameters.
typebug
Why is this aProblem:
Atlassian rolled out new authentication tokens for some installations, but the endpoint on GitLab was not ready to process the updates.
Workaround:
Reinstalling the app should fix this problem. WARNING: Uninstalling the app will remove all GitLab data from the Jira development panel. We are working on a better solution though.
Upcoming Solution:
We are able to fix the endpoint for installation updates on GitLab, but waiting to confirm that the authentication token updates can be sent again.
Note for self-managed users experiencing this issue
The issue has been fixed on GitLab in %14.9 but it requires an additional to get the app working again:
- Enable the
jira_connect_installation_update
feature flag on your GitLab instance. Here is a guide that explains how to do this. - File a support request to Atlassian, asking to retrigger the install hook for your GitLab app on your Namespace.