I would suspect there’s not many places where issues are enabled and not in use
I’m fine with your proposed process Thanks Tim On Thu, 17 Dec 2020 at 07:38, Richard Bywater <[email protected]> wrote: > Using the pom to explicitly point to where issue management is done seems > reasonable to me although I note from the docs ( > https://maven.apache.org/pom.html#issue-management) that there's a > "system" element and a "url" element so presumably rather than using some > unique format we could just use jira/github for system and the actual URL > for the component or Github repo issues link? > > Richard. > > On Thu, 17 Dec 2020 at 19:54, 'Gavin Mogan' via Jenkins Developers < > [email protected]> wrote: > >> Hey Everyone, >> >> I'm trying to upgrade/add Issue tracking support to the plugin site. We >> currently have a tab that lists issues from jira, but not all plugins are >> using jira, and it would be nice to have a direct link to issue tracker on >> the sidebar. >> >> The original plan was to default to JIRA unless Github Issues were >> enabled on the repo. But Daniel Beck pointed out that assumption might not >> be safe, github issues might be enabled but they are not used. >> >> Ideally I'd see the process being >> 1) Overrides file >> 2) Issue Managemnet section in pom.xml ( >> https://maven.apache.org/pom/maven/issue-management.html). I was >> thinking we should use jira:$component-name, or github:repo-name >> 3) Github if enabled >> 4) Jira >> >> I'm not even sure the data for #2 is exposed to poms and stuff. >> >> So looking for feedback on options and what people prefer. >> >> Gavin >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutC1CgDjwykf6pEbdKzDfvpR4W%2Bi%2B9GAuvLFRM_%3DQpdEg%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutC1CgDjwykf6pEbdKzDfvpR4W%2Bi%2B9GAuvLFRM_%3DQpdEg%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwc4m2eL_pPXEwm%3Da_zOGOzcRPw_p-LCxms17DfveJypwQ%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwc4m2eL_pPXEwm%3Da_zOGOzcRPw_p-LCxms17DfveJypwQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicN011%2B9jim%3DB_5JKs7xa9b5qnBNc5piLMVQH9_V30Phw%40mail.gmail.com.
