Guides/Roundup
From FGVwiki
Contents |
Roundup
Overview
Roundup is an issue tracking ticket system. The developers website is located here and documentation here. Primarily the issue tracking system is for general purposes, the login web address is http://roundup.freegeekvancouver.org/general/index also though there is a special ticketing system for hardware grants located at http://roundup.freegeekvancouver.org/hwgrant/index
Roundup in a Nutshell
Your tracker holds information about issues in bundles we call items. An item may be an issue (a bug or feature request) or a user. The issue-ness or user-ness is called the item’s class. So, for bug reports and features, the class is “issue”, and for users the class is “user”.
Each item in the tracker has an ID number that identifies it along with its item class. To identify a particular issue or user, we combine the class with the number to create a unique label, so that user 1 (who, incidentally, is always the “admin” user) is referred to as “user1”. Issue number 315 is referred to as “issue315”. We call that label the item’s designator.
Items in the database are never deleted, they’re just “retired”. You can still refer to them by ID - hence removing an item won’t break references to the item. It’s just that the item won’t appear in any listings.
Access
- Load this link and click on Register
- Fill out the detail and click submit.
Creating new users in hwgrants tracker
The hardware grant tracker is private, so new users have to be added by someone with permissionz and skillz.
- ssh <user>@hemlock
- sudo -u roundup roundup-admin create user
Enter tracker home: /var/lib/roundup/trackers/hwgrant
Username (String): alishams
Alternate_addresses (String):
Realname (String): Alishams
Roles (String): User role must be "User"
Organisation (String):
Address (String):
Phone (String):
Queries (Multilink):
Timezone (String):
Password (Password):
Password (Again):
Issue life cycles in Roundup
New issues may be submitted via the web or e-mail.
By default, the issue will have the status “unread”. If another message is received for the issue, its status will change to “chatting”.
The “home” page for a tracker will generally display all issues which are not “resolved”.
If an issue is closed, and a new message is received then it’ll be reopened to the state of “chatting”.
The full set of prority and status values are:
| Priority | Description |
| “critical” | panic: work is stopped! |
| “urgent” | important, but not deadly |
| “bug” | lost work or incorrect results |
| “feature” | want missing functionality |
| “wish” | avoidable bugs, missing conveniences |
| Status | Description |
| “unread” | submitted but no action yet |
| “deferred” | intentionally set aside |
| “chatting” | under review or seeking clarification |
| “need-eg” | need a reproducible example of a bug |
| “in-progress” | understood; development in progress |
| “testing” | we think it’s done; others, please test |
| “done-cbb” | okay for now, but could be better |
| “resolved” | fix has been released |
