# Issues and changesets not showing in build results

**URL:** https://www.finalbuilder.com/forums/t/issues-and-changesets-not-showing-in-build-results/5287
**Category:** Discussion
**Created:** [December 9, 2014, 10:07am UTC](https://www.finalbuilder.com/forums/t/issues-and-changesets-not-showing-in-build-results/5287 "2014-12-09T10:07:22Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![sid999](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/s/ccd318/32.png) [@sid999](https://www.finalbuilder.com/forums/u/sid999)
#### Post date: [December 9, 2014, 10:07am UTC](https://www.finalbuilder.com/forums/t/issues-and-changesets-not-showing-in-build-results/5287/1 "2014-12-09T10:07:22Z")

</div>

Hi  
  
I’m having a problem associating changesets/issues when performing a build.  
  
At the moment I have a Bitbucket git repository into which I have pushed a number of changes. Each of the changesets that have been created have an issue associated with them. When I go into Continua and perform an inital/first-time build using the code from this repository it only ever associates the last committed changeset and it’s related issue.   
  
I have tried performing this first-time build using both “associate” options, but I always end up with the lastest changeset/issue being associated with the build.  
  
What I would like, when I perform the first-time build, is to have all the existing changesets/issues currently in the repository associated with the build.  
  
Is this possible?  
  
Thanks

---

<div class="post-metadata">

### Author: ![Sparky](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/sparky/32/10_2.png) [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)
#### Post date: [December 10, 2014, 1:12am UTC](https://www.finalbuilder.com/forums/t/issues-and-changesets-not-showing-in-build-results/5287/2 "2014-12-10T01:12:47Z")

</div>

Hi Sid,  
  
This is not possible at the moment.  
  
We only load the last changeset on each branch when initialising a new repository. The reason for this is performance. Your repository could contain a large number of changesets and we need to build a cache of these for transporting to the agent. This can take a long time and we want you get you started building as soon as possible.&nbsp;  
  
We have an item on our to-do list to add option to the create repository dialog to allow you load in all (or a range of) previous changesets in a background process. I can’t, however, give you a date when this will be implemented.