-
Type:
Bug
-
Resolution: Answered
-
Priority:
Low
-
None
-
Affects Version/s: 4.6.0, 4.7.0, 4.8.0
-
Component/s: Code reviews, Indexing
-
Severity 3 - Minor
-
1
Issue Summary
When a user tries to list git branches on view changesets screen while creating review, some branches are missing.
The issue occurs when at least two branches point to same commit. Only one branch gets listed, the rest are missing.
The issue disappears when a new commit is pushed to one of the branches.
New branch is created from another (i.e. master) and pushed to remote without any new commits. This leads to the situation when two branches have exactly same commit as top commit. When trying to create review being in that state, one of the branches is missing.
Steps to Reproduce
- Prepare a repository (on github or bitbucket)
git clone https://github.com/[author]/[repo].git cd [repo]/ echo "foo1" > foo1.txt git add foo1.txt git commit -m "foo1" git branch new-branch git push --all
- Add the repository to FishEye and wait for it to be indexed
- Start creating review, go to Browse changesets and open the branches dropdown
Expected Results
All existing branches should be visible, i.e. master and new-branch from the prepared repo (see. Steps to reproduce, point 1.).
Actual Results
Only one branch is listed. Rest is missing (i.e. new-branch).
Workaround
A temporary workaround of the issue is to push a (empty) commit to one of the branches.