-
Bug
-
Resolution: Fixed
-
Low
-
8.20.30, 9.12.12
-
8.2
-
2
-
Severity 3 - Minor
-
5
-
Problem
When a user is removed from Gitlab but still have entries in AO_E8B6CC_CHANGESET_MAPPING.AUTHOR pointing at the deleted account it causes noise in the logs and NPE when the development panel data is visited , this is an unhandled scenario.
Environment
Jira 8.20.X
Jira 9.12.X
Any Gitlab on prem version
Steps to Reproduce
- Link Gitlab to Jira Linking GitLab accounts
- Add a commit pointing to a Jira ticket with user X
- Delete Gitlab user X or change the email on Gitlab to not match the previous value or the Author value in Jira changeset table
- Visit the ticket that the commit was made against and click on the commit link in the development panel
Expected Results
Jira will display the development panel without errors
Actual Results
Jira throws a null exception in the logs
2024-07-26 13:31:05,569+0000 devstatus.dvcs.gitlabselfmanaged:thread-7 INFO admin 810x664x2 1bnue8p 172.29.215.81,172.50.0.2 /rest/dev-status/1.0/issue/detail [c.a.j.p.dvcs.service.RepositoryServiceImpl] Could not load user [dummy@mail.com, dummy@mail.com] - java.lang.NullPointerException
Workaround
- Go to Administration->system->Logging and profiling->Default Loggers
- Configure logging level for another package and add the bellow packages as Fatal or OFF
- com.atlassian.jira.plugins.dvcs.service
- links to