On Thu, Jun 11, 2020 at 11:26 AM Jeff Thompson <jthomp...@cloudbees.com> wrote: > Jenkins is a system of interacting components and issues may involve multiple.
Every time I have worked with a Jira issue with multiple components, I have wound up regretting the resulting confusion. It gets marked fixed by one person due to a fix in one repository, but something else still needs to be done in another repository, etc. So long as a repository corresponds to an actual artifact and an actual version number, it is advisable to just have one issue per repository and link them textually as needed. (Once the code associated with the issue is clear! Before then, you can just transfer an issue.) While I generally find GH issues far more comfortable to work with, the search options are terrible compared to JQL. -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0ebVvD%2BVbu-38SnEZ5zWhEVrRgCOuDJ%3D-mNuh_QJ3DXA%40mail.gmail.com.
