h4. *JIRA* is a issue tracking and project management system that you access from your web browser.
The complete JIRA documentation from Atlassian is available [here|http://confluence.atlassian.com/display/JIRA/JIRA+User%27s+Guide].
To obtain a JIRA account, add a new project, and/or adjust permissions, please contact [Holly Mistlebauer|mailto:hlm7@cornell.edu].
{lozenge:title=Login to JIRA|icon=JIRA|link=http://issues.library.cornell.edu/|color=red}
{lozenge}
h6. JIRA consists of *Projects* that contain *Issues*
[What is an Issue?|http://confluence.atlassian.com/display/JIRA/What+is+an+Issue]
[What is a Project?|http://confluence.atlassian.com/pages/viewpage.action?pageId=185729449]
h6. [Customizing the Dashboard|http://confluence.atlassian.com/display/JIRA/Customising+the+Dashboard]
Have issues that are assigned to you show up on your JIRA Dashboard (aka home page).
Have easy access to your project(s), favorite filters, etc. as well.
h6. [Managing your User Profile|http://confluence.atlassian.com/display/JIRA/Managing+your+User+Profile]
Change your Password, Profile, and Preferences.
h6. [Creating and working with Issues|https://confluence.atlassian.com/display/JIRA/Working+with+an+Issue]
[Creating an Issue|http://confluence.atlassian.com/display/JIRA/Creating+an+Issue]
Create several issues within the "Move to New Library" JIRA project.
Assign one to yourself and one to someone else in the group.
Check your email to see the notification.
[Editing an Issue|https://confluence.atlassian.com/display/JIRA051/Editing+an+Issue]
Edit one or more issues that you created.
[Email an Issue|https://confluence.atlassian.com/display/JIRA051/Emailing+an+Issue]
Email one of your issues to a classmate who the issue is not assigned to.
[Creating a Sub-Task|http://confluence.atlassian.com/display/JIRA/Creating+a+Sub-Task]
Create several sub-tasks for the tasks you created above.
See how the sub-tasks appear when viewing the task.
[Commenting on an Issue|http://confluence.atlassian.com/display/JIRA/Commenting+on+an+Issue]
Add comments to the issues you created above.
[Attaching a File to an Issue|https://confluence.atlassian.com/display/JIRA/Attaching+a+File]
Attach a file to one of the issues you created above.
[Linking Issues|http://confluence.atlassian.com/display/JIRA/Linking+Issues]
Link one or more issues together.
*{_}Also try other features, such as reassigning an issue, moving an issue (move to CUL Sandbox JIRA Project), watching an issue, working on an issue, resolving an issue, etc._*
h6. [Searching for Issues|http://confluence.atlassian.com/display/JIRA/Searching+for+Issues]
[Using Quick Search|http://confluence.atlassian.com/display/JIRA/Using+Quick+Search]
[Searching for Issues|http://confluence.atlassian.com/display/JIRA/Searching+for+Issues#SearchingforIssues-Searchingforissues]
[Saving Searches (aka Using Filters)|http://confluence.atlassian.com/display/JIRA/Saving+Searches+(%27Issue+Filters%27)]
[Using the Issue Navigator|http://confluence.atlassian.com/display/JIRA/Using+the+Issue+Navigator]
[Customizing your Issue Navigator|http://confluence.atlassian.com/display/JIRA/Customising+your+Issue+Navigator]
Search for the issues you created.
Save your search.
Share you search with the training-users group.
Try the shared searches created by your classmates.
h6. [Generating Reports|http://confluence.atlassian.com/display/JIRA/Generating+Reports]
Take a look at the Project Summary for the "Move to New Library" JIRA Project.
Use Reports option to create Pie Charts, Gantt Charts, you name it\!
Can also create canned reports via the Filters option. The results can be printed or exported to Word, Excel, PDF, XML, etc.
h6. Using Components and Versions
[What is a Component? Version?|http://confluence.atlassian.com/pages/viewpage.action?pageId=185729449]
Watch instructor add Components.
Edit your issues to add a Component.
Search for issues assigned a specific component.
h6. [Browsing a Project|http://confluence.atlassian.com/display/JIRA/Browsing+a+Project]
*{_}All projects created should contain the following Schemes..._*
Permission Scheme (set which users are allowed to do what--done by Groups)
Notification Scheme (who should receive and e-mail when a change is made to the issue)
*{_}Other Schemes that are available include..._*
Issue Type Scheme (used if you want to have different issue types than the default)
Field Configuration Scheme (used if you want to have additional customized fields for entry)
Workflow Scheme (used if you want to have a non-standard workflow)
h5. JIRA Best Practices
* Don't send out e-mails about issues/tasks that are in JIRA. Simply keep all information in JIRA and let JIRA send e-mails when issues/tasks are added/updated.
* Attach documents to issues/tasks as appropriate, so all information is available in the future.
* Customize the issue/task entry page to meet your needs, including the addition of new custom fields.
* Customize the Notification Scheme so that folks do not receive unnecessary e-mails.
* Share reports (aka Filters) within the project.
* Make use of Versions so that all issues/tasks for a release/due date are reported together.
* Use Components to assign issues/tasks to the appropriate category. Each category can be assigned to the person in charge of that work.
* When using sub-tasks, give the parent task an estimate of 1 minute so that you able to quickly identify the parent tasks. | 
