You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
@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?
@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.
Add config option which lets a GitHub
milestone
map to a JIRAfixVersion
. 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.
The text was updated successfully, but these errors were encountered: