Project

General

Profile

Actions

Task #2642

closed

Update "Bug Status" text in Bugzilla

Added by Timur Gadzo over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
Team - Pool
Start date:
Due date:
% Done:

100%

Tags:

Description

"Bug Status" text in Bugzilla at https://bugs.documentfoundation.org/page.cgi?id=fields.html#bug_status should be updated.
Some missing, some not adequate explanation, some wrong with examples:
CONFIRMED -> NEW
IN_PROGRESS -> ASSIGNED

It should be correct and we should point reporters to that.

Actions #1

Updated by Timur Gadzo over 5 years ago

  • Project changed from Infrastructure to Documentation
Actions #2

Updated by Florian Effenberger over 5 years ago

  • Target version set to Pool

Project: Infrastructure

Xisco, your call :-)

Actions #3

Updated by Florian Effenberger over 5 years ago

  • Project changed from Documentation to Infrastructure
  • Assignee set to Xisco Fauli Tarazona

Xisco, your call :-)

Actions #4

Updated by Xisco Fauli Tarazona over 5 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Florian Effenberger wrote:

Xisco, your call :-)

Fixed in https://gerrit.libreoffice.org/gitweb?p=bugzilla.git;a=commit;h=c6d939d7957c05c096dc1cb2ee3090ea7e5fa67b.
I'll ask Guilhem to apply it to production.
Closing as RESOLVED

Actions #5

Updated by Timur Gadzo over 5 years ago

Not resolved. I gave examples, but more needs to be done.

Missing NEEDINFO in Open and NOTABUG, NOTOURBUG, INSUFFICIENTDATA, MOVED in Closed.

Wrong or missing explanations:

NEEDINFO
The report is not complete to determine whether described problem is a bug and we need additional information or test from the reporter. See https://wiki.documentfoundation.org/QA/BugReport.

INVALID
The problem described is not a bug. -> The problem described is not a proper bug report.

INSUFFICIENTDATA
The report doesn't give enough information or attach example document to follow up with bug triage.

WORKSFORME
All attempts at reproducing this bug were futile, and reading the code produces no clues as to why the described behavior would occur. If more information appears later, the bug can be reopened. -> Bug used to be reproducible, but is not anymore with current LibreOffice version. Unlike FIXED, exact fix commit is not known.

NOTABUG
The report is confirmed but it represents expected behavior and is not a bug.

NOTOURBUG.
The report is confirmed but it's not our fault and report should be submitted somewhere else, like OS or other office suite.

MOVED
The report is confirmed or seems justified but won't be resolved here and was moved or redirected where appropriate.

Actions #6

Updated by Xisco Fauli Tarazona over 5 years ago

Hi Timur,
Thanks for the detailed report. Fixed in https://gerrit.libreoffice.org/gitweb?p=bugzilla.git;a=commit;h=9f14abce2f835674689cf36fbc9c519fcf9d06e0
I'll ask Guilhem to apply it as well...

Actions #7

Updated by Florian Effenberger over 5 years ago

Is this done, can this ticket be closed?

Actions #9

Updated by Xisco Fauli Tarazona over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF