-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
3.9.0
-
None
-
Severity 3 - Minor
-
12
-
I can reproduce the problem on current FeCru snapshot "Version:4.1.0 Build:r46cc254 2016-06-06" as well, seems like a FishEye bug.
Just made 2 commits on a the test https://stash.atlassian.com/projects/TP/repos/fecru-test-sandbox/browse repository:
$ git log --format=medium HEAD^^..HEAD commit be188ff602d611f8d7d2e9f1ea149a46b8228eb8 Author: Piotr Święcicki <pswiecicki@atlassian.com> Date: Tue Jun 7 08:11:18 2016 +0200 FECRU-2547 and another change commit 6539aa4992b5a1a0d2ac0a98c0447bcbda493b50 Author: Piotr Święcicki <pswiecicki@atlassian.com> Date: Tue Jun 7 08:09:40 2016 +0200 FECRU-2547 - FECRU-2547 code changes
I can see JIRA https://jira.atlassian.com/browse/FECRU-2547 reports both commits in Stash, but only be188ff from FishEye.
Also, FishEye REST endpoint seems to report only be188ff commit, 6539aa4992b is missing: https://fisheye.dev.internal.atlassian.com/rest/remote-link-aggregation/latest/aggregation?globalId=FECRU-2547 (summary) and https://fisheye.dev.internal.atlassian.com/rest/dev-status/1.0/details/repositories?globalId=FECRU-2547 (details).
- is caused by
-
FE-5254 Jira issue keys wrongly matched to review keys
- Closed
- is incorporated by
-
FE-6687 Jira issue development panel shows wrong commits
- Long Term Backlog
- supersedes
-
JSWCLOUD-13751 Commits do not show in the Development Panel if the Issue Key is mentioned more than once in a commit message
- Closed
-
JSWSERVER-13751 Commits do not show in the Development Panel if the Issue Key is mentioned more than once in a commit message
- Closed