Feature Request - Support multiple Git repos, Jira projects

[lhriley]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

This project looks interesting, and I'm curious to try it. However, at scale it would be difficult to manage.

For example, we have many Jira projects and many Github repos. Each project and each repo might have some relationship due to how tasks are distributed to developers.

Example:
devA might be working on repoA and tickets are tracked in jiraA.
However, devB might work on repoA in jiraB, devC might work on repoB in jiraC, etc.

Describe the solution you'd like
A clear and concise description of what you want to happen.

I can see a few possible solutions:

1. Allow some kind of map that describes relationships between Jira and Github
2. Read the configuration from each git repo's default branch when appropriate events are detected
3. Use labels to associate Jira and Github on a per-issue basis

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Exploring alternatives now. For us, it sounds like if we wanted to try this it would require running a standalone octosync for each pair of github repo and jira project.

Additional context
Add any other context or screenshots about the feature request here.

The end goal would be to reduce the footprint required to run this as a service at scale. I would want just one octosync running to sync all of our issues across all of our Github / Jira projects.

[marcelovicentegc]

Hi, @lhriley! This feature would be awesome!

Allow some kind of map that describes relationships between Jira and Github

It occurs to me that the introduction of this map would do the job, indeed ☝️

Please, feel free to open a pull request 🙏