A knowledge base article about Jira Services Overview provided by the UC Berkeley IT Service Hub - Knowledge Portal
JIRA is a task management and project management tool available to enterprise application development teams supporting campus-wide enterprise applications. JIRA provides workflow management for teams to track defects, issues, enhancement requests, tasks, and deadlines. The ability to organize and track issues facilitates collaboration among project teams to improve code quality and the speed of development. Campus Applications & Data has licensed JIRA from Atlassian and offers it to teams developing/supporting campus-wide applications.
Campus Applications and Data, Application Delivery.
The use of Jira complies with general UC Berkeley policies as follow.
You may not store restricted data in Jira. See guidelines on restricted data.
This Service is the property of the Regents of the University of California at Berkeley and is for official University business only. In using this service you are subject to applicable University policies, law, procedures, or collective bargaining agreements. Misuse may result in the loss of access privileges, prosecution and/or administrative discipline under applicable statutes. Do not use this service if you do not agree to the conditions in this warning. Jira is NOT to be used for personal websites. If you encounter perceived misuse of Jira, please refer the problem to abuse@security.berkeley.edu.
JIRA is organized into projects. A project might be a software application or a group of tasks related to the building of a software application. A project can have components allowing a granular definition of its relevant parts. Issues are created for a specific project and can be assigned to the appropriate team member. As project leads, analysts, developers, etc... work on an issue, it is transitioned through workflows and managed by permissions supporting the software development lifecycle. Team members can comment on issues and view the issue history log file to understand the changes made during an issue's lifecyle.
Campus application development teams developing and/or supporting campus-wide enterprise applications may request a Jira project for their teams by submitting a request to jira@berkeley.edu. All Jira work sharing the same workflow, administrator(s), and team will be created as one Jira project, and related work grouped by components.
The request for a project should include the following information.
⚠️A deleted project is gone forever. It cannot be recovered.
Archiving a project removes it from Jira and preserves the data. Archiving inactive or completed projects keeps Jira tidy and improves overal better performance of our Jira instance.
Archived project data is ignored in the index, and removed completely after re-indexing Jira. This improves performance by removing data that is stored directly in Jira.
Archived projects can be restored but deleted project cannot be restored.
If you are new to JIRA, you may want to check out the following, JIRA - Administering Your Project
Note: Project administrators are responsible for requesting new user accounts. Only active UCB employees are eligible for a licensed Jira account. Project administrators are responsible for adding users to roles within their project.
Project administrators may request adding users by sending an email to jira@berkeley.edu. The request for adding a user to Jira must include the following information for the user they would like added to Jira.
Note: Only project administrators may request to have users added to Jira.
Project administrators are responsible for notifying Jira system administrators when users no longer require access by sending an email to jira@berkeley.edu and including the name and UID of the user to be removed from Jira.