Struggling with fundamentals

[Stephen Scaggs]

We have Jira, Confluence, and Bitbucket and are in the early stages of deployment. These tools appear to be able to meet our needs, but configuring them the uncertain part.  I've tried to search documention, community, etc., but I'm not using the correct key words.  I'll descibe one possible scenario and would appreaciate any help/guidance.

Imagine a project R1.  This R1 project contains software components: A1.1, B2.2, C3.3. 

Then C3.3 is updated to C3.4, thus R1 now becomes R2 with the software components: A1.1, B2.2, C3.4. (All arbritrary numbers for example only)

I've seen the methodology of putting the Jira issue id in the Bitbucket commit, thus 'tying' the issue to the Bitbucket version/tag/commit.  What I can't figure out is how I can pull it all together; we want to be able to run a report/view at the R1/R2 level and see all the subcomponents and the associated Jira issues contained within; we can see history of the project(s) and it's associated software components.

This seems VERY fundamental; obviously I'm missing something.