infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <>
Subject [jira] [Commented] (INFRA-16766) Git commits logged to JIRA have the wrong name.
Date Sat, 14 Jul 2018 01:36:00 GMT


Chris Lambertus commented on INFRA-16766:

The behavior is deterministic, but is based on a loose matching algorithm that looks at all
accounts on Jira which are remotely similar, so if someone adds a new account that looks close
to yours, it may end up popping up in the search result as the first entry, and will likely
continue to do so until someone else adds another account that changes the match output. This
loose matching is clearly a bug on Atlassian's end, but they staunchly refuse to address it.
At some point soon we are planning on updating the algorithm that does the matching on our
side to deal with it.

> Git commits logged to JIRA have the wrong name.
> -----------------------------------------------
>                 Key: INFRA-16766
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Git, JIRA
>         Environment: Jena uses github as a mirror.
>            Reporter: Andy Seaborne
>            Priority: Major
> has commits "from Andy Clark" who is
andyc\@apache, but the commit is actually from Andy Seaborne who is andy\@apache.
> The commit comment is:
> {noformat}
> Commit 8980491c16bc9ce47daccfb484920c3a8ced8769 in jena's branch refs/heads/master from
Andy Clark
> [;h=8980491 ]
> {noformat}
> The git commit,;h=da942d3,  has the
right information. It is just the JIRA comment that is wrong.
> Previous commits recorded to JIRA have this right - example:

This message was sent by Atlassian JIRA

View raw message