Firstly, we use the Jira integration in plastic so I only have experience in this area. I assume the same concepts apply to other trackers but I can only speak from my experience with Jira

Recently, we moved from using a number of xlinked repositories to using a MonoRepo in Plastic. It's no surprise that plastic already has good support for the MonoRepo approach.

One area we have found that is lagging a little behind is the issue tracker integration though.

Currently, the relationship for the Jira integration in plastic assumes a mapping of 1 to 1 for a repository to a Jira project. In a MonoRepo this becomes problematic because we still track our issues in multiple Jira projects but all of those projects are stored in a single Plastic Repository.

Here's a few things that I think could be improved
- Allow a wildcard in the "Prject Key" field when configuring integration for a plastic repository. This would mean that Plastic should find all tasks in all projects for my user rather than in a single project.
- Provide more options for branch names. This is to do with when you create a new branch from a Jira task. Currently, there's a "Branch Prefix" setting in the integration options. This doesn't apply for a MonoRepo. We in fact do not wish to apply a prefix at all but would prefer to use the entire Jira task key such as MYPROJ-12324. This would mean that the task key may be PROJ-001 or XYZ-002 depending on the Jira project it belongs to. Two options that a user might be able to select for the branch name option might be something in the form of "Use Jira Task Key" OR "Use Jira Task Id with custom prefix"