+1 for the proposed solution because you could also have two issues describing a different problem but with the same fix.
Thanks, Adel On Thu, Jan 10, 2019 at 1:37 PM Vincent Massol <vinc...@massol.net> wrote: > > > > > On 10 Jan 2019, at 13:24, Marius Dumitru Florea > > <mariusdumitru.flo...@xwiki.com> wrote: > > > > On Thu, Jan 10, 2019 at 12:43 PM Vincent Massol <vinc...@massol.net> wrote: > > > >> Hi devs, > >> > >> Right now we often use “duplicate” when we have an issue that is solved by > >> another issue (usually a more specific one). This is not semantically > >> correct. > >> > >> Proposal: > >> * Add a new jira resolution named “Solved by” > >> * Best practice: when using “solved by”, also use the “depends on” link > >> > >> WDYT? > >> > > > > +0 > > > > We could also close the "duplicate" issue as Fixed (so no new resolution) > > and add instead a "Fixed by" relation / link type. The users will see the > > issue as Fixed and the developers will see the link to the actual fix. > > I can think of some potential problems: > * Duplicates in the release notes generated by JIRA > * Missing tracability in the commits (it would need that the commit be > referencing the 2 jira issues) > > Note: FTR just checked and JIRA supports adding new issue links so that’s > doable: https://jira.xwiki.org/secure/admin/ViewLinkTypes!default.jspa > > Personally I prefer the proposed solution because of these 2 problems. I > don’t see any drawback for the proposed solution ATM (except additional > knowledge to have to use our jira best practices which would also be true for > this new proposal). The only thing that comes to mind is whether we’ll be > able to choose easily between “duplicate” and “solved by” when we start using > it. If we find that it’s hard to use then I agree we should revisit it then > and either drop the idea fully and go back the previous state or try > something else (like this new proposal). > > Thanks > -Vincent > > > > > Thanks, > > Marius > > > > > >> > >> Thanks > >> -Vincent >
