...
Added "Estimated End Date" as a field for all issues. The Estimated End Date will be used by developers to track when they think a task will actually be finished. This will allow others to know whether a task will be delivered earlier or later than its due date. This will be valuable to those whose tasks are dependent on other tasks being finished." It's a DatePicker type and is searchable as a range. In practice it will be valuable only to the extent that we actually use it and set it. This field is available in all projects so anyone who wants to use it can.
Introduction
What is JIRA?
JIRA is a next-generation issue tracking system, implemented in Java as a Java Servlets application (.war).
"Issue tracking"? Don't you mean "bug-tracking"?
JIRA is more than bug tracking. JIRA isn't just about characterizing the failings of released software. JIRA is about project planning. It allows you to schedule bugfixes alongside feature additions and enhancements and administrative tasks. It provides a "Roadmap" creation feature.
Yeah, yeah. This is just Bugzilla with some slick CSS.
Fair enough. If the lickable GUI helps people be excited about resolving issues in our products, we're all for it.
Why are you using a commercial product in support of your open-source effort? Don't you have any principles, or at least some pride?
The uPortal community believes in open-source software and its principles, but we are not so literal or narrow-minded to exclude commercial tools from our toolbox. We believe in open-source because we value the sharing of solutions, collaboration, and communication producing quality open-source software requires. JIRA is a tool that allows us to be more effective in that collaboration.
Using JIRA
Issue statuses
Icon | Name | Comment |
|---|---|---|
| Open | The issue has been reported by someone, but no actual progress has been made on it. If the issue is assigned to a developer, that developer has not begun to actively work 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 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. |
JA-SIG Jira administration
Where is it being hosted?
This JIRA instance is generously hosted at Princeton University under the auspices of the JA-SIG / Clearinghouse efforts. While credit is most certainly due to the Clearinghouse community for making this happen, it seems that we will all be less confused if we reserve the term "Clearinghouse" to refer to the specific uPortal instance called "Clearinghouse" and say at this JIRA instance is hosted by "JA-SIG".
Who is administering it?
This JIRA instance is administered at the JIRA application level by the members of the JIRA group "jira-administrators". See below for the membership of this group.
How do I get an administer to execute an administrative task for me?
First, be sure it's an administrative task. Management of individual projects hosted in JIRA has been delegated to the individual project administrator groups. Your request may be something best handled at that level.
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. |