How to organize control over the development of a modular system?

Question

Bitbucket

Good day!
I decided to create a system of kicking boots for myself: I added several repositories to bitbucket, created an account in slack, set up synchronization, I'm thinking about trello, but for now I decided to get by with issuses in bitbucket.
Several repositories:

• Server
  
• Customer
  
• Library 1
  
• Library 2
  

I think to add a few more repositories for each individual module.
I stopped, looked around, thought...
If I spawn so many repositories, will I get confused in their management, despite the Divide and Conquer principle? After all, everyone will have their own bug tracker. And the system as a whole is unified, and numerous bug trackers may not be able to cope with the transfer of a single problem.
On the contrary, each module has its own separate isolated control systems - this is good: there will be no dump on BitBucket, it will be in slack, but that's what it is for, to be a convenient dump.
Would love to hear from people with experience in similar situations.

Answer 1

keep one tracker, a link to which you place in each repack.