+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 wrote:
>
>
>
> > On 10 Jan 2019, at 13:24, Marius Dumitru Florea
> > wrote:
> >
> > On Thu, Jan 10, 2019 at
> On 10 Jan 2019, at 13:24, Marius Dumitru Florea
> wrote:
>
> On Thu, Jan 10, 2019 at 12:43 PM Vincent Massol 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
>>
On Thu, Jan 10, 2019 at 12:43 PM Vincent Massol 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”
> *
I have no problem with the "Duplicate" resolution. It's very explicit. Some
issues have multiple manifestations, but a single cause.
On Thu, Jan 10, 2019 at 12:45 PM Thomas Mortagne
wrote:
> On Thu, Jan 10, 2019 at 11:43 AM Vincent Massol
> wrote:
> >
> > Hi devs,
> >
> > Right now we often
Hi,
I'm +1 to have the "Solved by" and since this will have only one purpose, I
don't see the need of the extra "depends on". If possible, we should link a
related issue with the same marker.
Thanks,
Alex
On Thu, Jan 10, 2019 at 12:45 PM Thomas Mortagne
wrote:
> On Thu, Jan 10, 2019 at 11:43
On Thu, Jan 10, 2019 at 11:43 AM Vincent Massol 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”
> *
On 10/01/2019 11:43, Vincent Massol 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
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
8 matches
Mail list logo