Jira integration relinking old commits
Summary
The Jira integration of Gitlab relinks old commits seemingly at random
Steps to reproduce
thus far unknown, I don't know what triggers this behavior.
What is the current bug behavior?
On 17 December 2019 a user made a commit on our Gitlab CE instance linking it to Jira ticket VX-12040. This commit was correctly linked to its jira ticket. On 9 march 2020 Gitlab suddenly linked this commit to the issue again (causing Jira to notify the user even tough the ticket was already closed)
- There is a difference between the links. The original link (17 December) looks like: https://git.somewhere.com/group/project/commit/b4ece197a7bfba4ca05127df30522b8c011f4f4f
- The wrongly added 9 march link looks like: https://git.somewhere.net/group/project/-/commit/b4ece197a7bfba4ca05127df30522b8c011f4f4f (notice the /-/)
note 1: this ticket or commit have not seen any related activity since 6 January 2020.
note 2: in this ticket I describe one case of this issue. It happens once or twice per week.
note 3: No commits where made on 9 march around 7.30 PM
What is the expected correct behavior?
I would have expected Gitlab to link the ticket only once when it was relevant.
Relevant logs and/or screenshots
I redacted pictures and names that are not my own
The commit on Gitlab:
the Activity of the Jira ticket (the two redacted names in the VSM Gitlab
posts are the same):
Time path of when things happened related to the commit:
13 November 2019: ticket was created
17 December 2019: ticket was taken into progress
17 December 2019: the commit was made, Gitlab linked it to the ticket
2 January 2020: A merge request containing the commit was opened (ticket was not mentioned in the description)
6 January 2020: The merge request was completed
6 January 2020: the ticket was closed
9 March 2020: the commit from 17 December was mentioned by Gitlab in Jira
I don't know what version of Gitlab CE we where running around 17 December. On 9 march we ran on version 12.8.1 d18b43a5f5a.