Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitHub Project lookups assume there can only be one GitHub Project #272

Open
mattreid opened this issue Dec 19, 2024 · 0 comments
Open

GitHub Project lookups assume there can only be one GitHub Project #272

mattreid opened this issue Dec 19, 2024 · 0 comments

Comments

@mattreid
Copy link
Collaborator

While it is now possible to sync GitHub Project metadata down into Jira, the current implementation assumes that there can only be one GitHub Project to look at, so users can't specify more than one. There's at least one team that is using sync2jira and GHP, and has a subset of their repos which should map to two GitHub Projects to more accurately reflect that either team may pick up issues in there (most of their repos are more clear cut and 1:1). Even if a repo mapped to two GHPs, only one team would work any particular issue, so it would likely be the case that if sync2jira queried both GHPs, it would only find information relevant to that issue in one of them, so there wouldn't be conflicting values to try and determine between. If there were an edge case where more than one GHP returned information, that would be trickier to handle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant