Bugzilla Replaced by JIRA
Thanks to ~edalquist Eric Dalquist, uPortal's original issue tracking system, Bugzilla, has been officially replaced by JIRA. All of the issues from Bugzilla have been imported into JIRA so that we retain the history. Fortunately, the Bugzilla bug numbers have been preserved so that old release notes that contain Bugzilla numbers will still be meaningful. Note that uPortal 2 and uPortal 3 are represented as different projects in JIRA.
...
Icon | Name | Comment |
|---|---|---|
| Open | The issue has been reported by someone, but no actual progress has been made developer actually considers himself or herself to be currently working on it. If the issue is assigned to a developer, that developer has not begun to actively work on the bug, or is no longer actively working on the bug. Open bugs are typically fair game for other developers to take ownership of, work on, and resolve. |
| In Progress | The assignee is actively working on this issue. Reassigning bugs away from a developer who considers them "In Progress" without communicating with that developer is anti-social. |
| Resolved | The assignee of the issue (the programmer on the scene) believes the issue has been fixed. It is now up to the original reporter to verify the fix. If the reporter verifies the fix, he or she should mark it "Closed". If the reporter finds that there has been some misunderstanding about whether the issue is "fixed", he should communicate with the assignee (the programmer) and mark the issue "reopened". Either way, issues should not languish in the "Resolved" state. |
| Reopened | The reporter does not agree that the issue is resolved and so has moved the issue out of the resolved state and back into the reopened state. |
| Closed | The issue reporter has verified that the issue is resolved. |
...
If you discover that what needs done does require the intervention of a "jira-administrator", please make your request on the JASIG-DEV list. An advantage of having a number of JIRA administrators is that there are more hands to do this sort of work when necessary.
Specific JIRA projects
Code | Project | Permissions | Change notifications |
|---|---|---|---|
BOOKMARKS | Bookmarks channel | uPortal standard | Posted to this list |
BCP | Briefcase Portlet The Briefcase Portlet JIRA project tracks issues in and progress of, including future release plans for, the Briefcase Portlet, which is a portlet allowing uPortal users to access their institutional fileshare via uPortal. | Administered by "briefcase-admin". | Posted to this email list. |
CAS | The CAS JIRA project tracks issues in and progress of, including future release plans for, the CAS 3.0 efforts. It is not currently used to track CAS 2.x. and earlier, though the use of this project is still in evolution. CAS is the Central Authentication Service, initially developed by Yale University and now an evolving join effort of Yale, Rutgers, and the larger JA-SIG Community. | Administered by "cas-admin". Developers on this project are "cas-devel". | Posted to this email list. |
CH | Clearinghouse |
| Posted to this email list. |
TST | "TEST" is a test JIRA project. It's a playground where you can try out JIRA, try submitting an issue, commenting on an issue, resolving an issue, without introducing noise into the JIRA projects that are being used to track operating projects. | Most permissions are granted to most users to maximize the usefulness of this space as a place to try out JIRA. | Changes to TEST are not posted to a list. |
GAP | Groups and Permissions | Administered by "gap-admin". | Posted to an email list. |
UBCWEBMAIL | UBC Webmail | As uPortal | Posted to this an email list. |
UP | uPortal: This project models the uPortal 2.x line of work. |
"uportal-admin" administers this project. "uportal-developers" take, edit, schedule, and resolve issues.|Posted to this email list.|
UPD | uPortal documentation | "uportal-doc-leads" administers this project. "uportal-developers" and "uportal-doc-contrib" take, edit, schedule, and resolve issues. All developers are documenters, and there are some additional documenters who are not developers. | Posted to this email list. |
UPT | uPortal 3: This JIRA project models progress and issues in the uPortal 3 codebase. It will be used to plan milestone releases and after 3.0 release it will be used to plan the future of this code. | "uportal-admin" administers this project. "uportal-developers" take, edit, schedule, and resolve issues. | Posted to this email list. |
A full list of projects is available in Jira via the Browse Projects page. Projects are grouped into related categories to help ease navigation.
Each project has an associated notifications email list. The specific lists are enumerated on the Existing Email Lists page.