Differences between revisions 6 and 7
Revision 6 as of 2014-05-05 14:33:17
Size: 3330
Editor: RDavidMurray
Comment:
Revision 7 as of 2014-08-06 20:42:15
Size: 3399
Editor: EzioMelotti
Comment: Mark the clip icon suggestion for patches as done.
Deletions are marked like this. Additions are marked like this.
Line 102: Line 102:
* Show a "clip" icon in the issue list page for issues with a patch * **DONE** Show a "clip" icon in the issue list page for issues with a patch (see http://psf.upfronthosting.co.za/roundup/meta/issue550)

This page outlines a plan to improve the Bug Tracker at http://bugs.python.org.

See also the TrackerDevelopment page and the DesiredTrackerFeatures pages.

Workflow

Certain things in the UI may trigger depending on how the user is classified. The current roundup 'Developer' role is modified into the following sub-roles:

  • Triage
  • Committer
  • Release Manager

Change possible 'resolved' states to the following:

  • fixed
  • won't fix
  • duplicate
  • postponed
  • not a bug
  • third party

Replace both 'components' and 'keywords' by a more comprehensive tagging system. Initially at least these will all be 'official' tags, listed in the developer's guide and settable via autocomplete in a text field. The list of values should be every category currently in the experts list, plus:

  • resource usage
  • performance
  • security issue
  • segfault/abort
  • stuck
  • buildbot
  • bite sized
  • release blocker (for each active release)
  • deferred blocker (for each active release)

Change Types to:

  • documentation
  • bug
  • enhancement

Change 'assigned to' so that it can be any valid user, and it is automatically reset to 'no one' after N days or an issue state change.

New 'state' field will eventually replace both 'stage' and 'status'.

  • new
  • information needed
  • decision needed
  • patch needed
  • review needed
  • patch update needed
  • commit review needed
  • resolved (with one of the resolved states)

Priority:

  • high
  • normal
  • low

Other features

User Interface

  • Have only title/message/state in the default user view, with a sticky (either per-user or per-browser (via cookies)) setting to also show the other fields. (No 'state' in the 'new issue' view).
  • Show the role of users (normal user, developer/triager, committer) with an icon or tooltip
  • DONE Show a "clip" icon in the issue list page for issues with a patch (see http://psf.upfronthosting.co.za/roundup/meta/issue550)

Dashboard(s)

Add a dashboard page similar to https://dashboard.djangoproject.com/ (global + per user?).

Experiment with a dashboard that actually lists the top messages in each state, arranged in the order of interest to the user based on their role (user, triager, committer).

'stuck' issues are sorted to bottom of queue.

'information needed' queue should list only issues that have been in that state for longer than N days.


CategoryTracker

TrackerDevelopmentPlanning (last edited 2016-01-05 05:47:11 by EzioMelotti)

Unable to edit the page? See the FrontPage for instructions.