# Branch analysis

**URL:** <https://community.sonarsource.com/t/branch-analysis/28567>\
**Category:** Suggest new features\
**Tags:** sonarqube\
**Created:** [July 23, 2020, 3:35pm UTC](https://community.sonarsource.com/t/branch-analysis/28567 "2020-07-23T15:35:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![aanvekar001](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/aanvekar001/32/10855_2.png) [@aanvekar001](https://community.sonarsource.com/u/aanvekar001)\
**Post date:** [July 23, 2020, 3:35pm UTC](https://community.sonarsource.com/t/branch-analysis/28567/1 "2020-07-23T15:35:01Z")

</div>

Hi Team,

I am doing branch analysis, and I don’t want the issues to carry forward.  
Example:  
Let us consider I created 2 identical branches A & B.  
I make some updates in branch B and there are few bugs raised.  
I mark those issues as false positive in SonarQube and merge the code to A.  
Now I run the analyses against A, and I still see those bugs showing up in A(which are already marked as false positive in B).

Is this default behavior? how do I make those issues not appear in my branch A? as I have already take care in Branch B.

Thanks,  
Abhishek

---

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [July 23, 2020, 5:36pm UTC](https://community.sonarsource.com/t/branch-analysis/28567/2 "2020-07-23T17:36:08Z")

</div>

Hi Abhishek,

What version are you using?

&nbsp;  
Ann

---

<div class="post-metadata">

**Author:** ![aanvekar001](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/aanvekar001/32/10855_2.png) [@aanvekar001](https://community.sonarsource.com/u/aanvekar001)\
**Post date:** [July 24, 2020, 12:19pm UTC](https://community.sonarsource.com/t/branch-analysis/28567/3 "2020-07-24T12:19:50Z")

</div>

> [@ganncamp](#):
>
> What version are you using?

version: 8.3

---

<div class="post-metadata">

**Author:** ![dmeneses](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/dmeneses/32/2933_2.png) [@dmeneses](https://community.sonarsource.com/u/dmeneses)\
**Post date:** [July 29, 2020, 8:01pm UTC](https://community.sonarsource.com/t/branch-analysis/28567/5 "2020-07-29T20:01:59Z")

</div>

Hi,  
That’s not the expected behavior. Normally when branch A is analyzed, it finds the matching issues in B and reuses their resolution (false positive). However, sometimes SonarQube might not find the matching issues for several reasons. For example, if a file gets renamed/moved or if the code gets changed in a way that our algorithm fails to match the same issue in both branches.  
If you have a simple reproducer of the problem (code of both branches), I’d be happy to look at it and see what’s happening.