#832: add an explanation why ABRT thinks that something is a dupe
-----------------------+----------------------------------------------
Reporter: jmoskovc | Owner: crash-catcher@…
Type: defect | Status: new
Priority: major | Milestone: ABRT_server_Bugzilla_Integration
Component: faf | Version:
Resolution: | Keywords: Nov2012
Blocked By: | Blocking:
-----------------------+----------------------------------------------
Old description:
> - when ABRT server finds a duplicate it should add a comment to the
> ticket why it thinks it's a duplicate and what is expected from the
> maintainer to do with it (this should explain as kindly as possible why
> so many reports ends in the one ticket)
>
> - the maintainer should be able to understand why ABRT thinks it's a
> duplicate and if it's a flase positive he should add a comment why it's
> not a duplicate and reassign to proper component
>
> - there should also be an easy way how to inform the server that it was
> a false positive, so it won't match new reports, I'm thinking about a
> link which developer can just click like:
>
> https://retrace.fedoraproject.org/faf/falsepositive/report_id/rhbz_id
>
> - which would say to ABRT that the $(report_id) is not a dupe of rhbz_id
> without too much effort from the developer and we could investigate this
New description:
- when ABRT server finds a duplicate it should add a comment to the ticket
why it thinks it's a duplicate and what is expected from the maintainer to
do with it (this should explain as kindly as possible why so many reports
ends in the one ticket)
- the maintainer should be able to understand why ABRT thinks it's a
duplicate and if it's a flase positive he should add a comment why it's
not a duplicate and reassign to proper component
- there should also be an easy way how to inform the server that it was a
false positive, so it won't match new reports, I'm thinking about a link
which developer can just click like:
https://retrace.fedoraproject.org/faf/falsepositive/report_id/rhbz_id
- which would say to ABRT that the $(report_id) is not a dupe of rhbz_id
without too much effort from the developer and we could investigate this
- it should also add a maintainers all components affected by the same
problem in the ticket (right now only the maintainer of the first crashes
component knows about it) - this way hopefully one of the maintainers will
take a look at it (note: when maintainers start complaining about adding
them to CC on too many tickets, they should understand that if it was the
old way they all would have a separate tickets and this way is more
"common effort")
--
Comment (by jmoskovc):
- the problems can be re-grouped (re-clustered) sometimes, but this
doesn't happen too much, so let's worry about that later ... (like
removing the devels whose component is not longer in the problem group)
--
Ticket URL: <https://fedorahosted.org/abrt/ticket/832#comment:1>
Automatic Bug Reporting Tool - ABRT <http://fedorahoted.org/abrt/>
Automatic bug reporting tool
