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

Map GitHub Milestones to JIRA FixVersions #148

Open
adambkaplan opened this issue Apr 5, 2024 · 3 comments
Open

Map GitHub Milestones to JIRA FixVersions #148

adambkaplan opened this issue Apr 5, 2024 · 3 comments

Comments

@adambkaplan
Copy link

Add config option which lets a GitHub milestone map to a JIRA fixVersion. This should be configurable per repository.

This can only be realistically done one GitHub milestone at a time today with filters and hard-coding JIRA fix versions in the config. This won't scale to upstream repositories that have stable/LTS releases that use milestones to track backports.

@adambkaplan
Copy link
Author

adambkaplan commented Apr 5, 2024

It looks like this might in fact be supported code? However the documentation does not provide a good, concrete example.

@Zyzyx
Copy link
Collaborator

Zyzyx commented Jun 24, 2024

@ralphbean what is the history with this one? What's the use case for the mapping config option?

@adambkaplan are you looking to have a mapping where GitHub milestone A maps to Jira fixVersion X, assuming X exists in Jira already, or something more complex?

@adambkaplan
Copy link
Author

@Zyzyx I think @ralphbean helped me out here. However the milestone mapping relies on GitHub numeric IDs for milestones. These are not easy to find in the GitHub UI - the name of the milestone is most familiar.

Support for milestone names would be nice, but potentially brittle. Maintainers can change milestone names at will. Documenting that you need to specify the numeric ID is fine by me.

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

2 participants