Documentation for JIRA 5.2. Documentation for other versions of JIRA is available too. 
![]()
17 May 2012
JIRA 5.1 Beta 1 is a public development release leading up to JIRA 5.1. A Beta release is part of our Early Access Program (EAP) and is a more mature snapshot of our work in progress, primarily focused on allowing JIRA users to see new features in advance of an upcoming major release and providing us with some useful feedback. EAP releases also give plugin developers an opportunity to test and fix their plugins in advance of an official release. For all production use and testing of JIRA, please use the latest official release.
The Atlassian team is proud to bring you the release of JIRA 5.1 Beta 1. Thank you for your feedback during earlier JIRA 5.1 EAP releases and please keep providing your feedback here.
Be aware that a few of the features in this JIRA 5.1 EAP release (described below) were also included in previous JIRA 5.0.x releases.
Upgrading to JIRA 5.1 Beta 1:
Not only is JIRA 5.1 more efficient for working with issues, but improvements to the core performance of JIRA 5.1 makes all of JIRA, especially creating, editing, searching for and viewing issues, faster and more scalable than ever.
Inline editing and fewer page reloads | Enterprise scale and performance improvements | Issue collector |
| ||
|
|
|
Do not use in production
JIRA 5.1 makes working with issues faster with inline editing and fewer page reloads.
You can now directly modify an issue's fields when viewing an issue, without the page needing to reload (top-left screenshot).
When viewing an issue, simply click on a field's content to begin editing it. Once you've finished editing, simply click on the lower-right tick icon (or in a blank area away from the field you're editing) to save your changes – no page reload required.
For keyboard fans, inline editing provides its own keyboard shortcuts, which means you can avoid having to use a mouse when editing issues. When viewing an issue:
Inline editing is enabled by default on new and upgraded JIRA installations. From JIRA 5.1 EAP 2, JIRA administrators can disable this feature by switching the Inline edit option to OFF through the General Configuration page.
Quick tips:
After performing an operation on an issue, such as adding a comment to an issue or performing a workflow transition (like the customised transition shown in the lower-left screenshot), JIRA updates the issue immediately without the page needing to reload.
The following performance improvements are available:
The JIRA Configuration Tool now includes an Advanced database connection tuning page which allows you to fine tune your database connection pool and validation query settings. This may be required with some default database configurations to maintain a successful connection between your JIRA server and JIRA database.
To help diagnose performance problems in JIRA associated with database connectivity, JIRA system administrators now have access to the new Database Monitoring page, which shows a graphical representation of JIRA's database connection usage over time.
JIRA system administrators can access this page by selecting Administration > System > Monitoring which opens the Database Monitoring page.
Keyboard Shortcut: g + g + start typing monitoring
The issue collector, initially bundled with JIRA 5.1 Beta 1, allows you to easily embed a JIRA feedback form into a different web site, which when used by people visiting that site, creates issues in JIRA.
JIRA project administrators can begin this process by simply visiting their JIRA project's Project Summary administration page (via Administration > Projects) and clicking the Issue Collectors tab on the left.
After configuring an issue collector, JIRA generates a JavaScript or HTML snippet for it, which creates a tab on any pages of your web site that includes this code.
When anyone visiting your web site clicks this tab, a dialog box appears (similar to the example screenshot on the left) which upon submission, conveniently creates an issue in your JIRA project. Visitors clicking this tab don't require a user account in JIRA.
JIRA now makes editing a project's workflow much easier. When you begin editing a project's workflow for the first time, you'll be able to modify that workflow almost immediately, since JIRA automatically makes a copy of the system workflow (jira) and associated workflow scheme for your project, and then associates this new workflow scheme with your project, all from the click of an icon.
To begin editing a project's workflow, simply click the pencil icon on the project's Workflow page (shown in the top-left screenshot).
Note also that:
Following on with improvements to the administration user interface in earlier JIRA releases:
A JIRA user who either creates a new issue or comments on an existing issue, will automatically become a watcher of that issue.
This feature applies to all new and existing JIRA users in a new (or upgraded) JIRA 5.1 installation.
If you don't want to automatically become a watcher of an issue you create or comment on, you can disable this feature through your user profile, by choosing Disabled for the Autowatch option when editing the Preferences section of your user profile (see left screenshot).
Linking to issues is now easier than ever with the following improvements to the Link dialog box:
If you're installing JIRA for the first time, you'll be presented with a new welcome page to help guide you through the process of creating your first JIRA project. There is also no need to log in after running through the JIRA Setup Wizard.
After creating a new project through the welcome page, you'll be taken directly to the project's Summary page (instead of the Project Summary administration page).
When creating a new project, the Add a new project dialog box now suggests a project key based on the name you specify.
If you're faced with the task of creating multiple users in your JIRA site, you'll be happy to know that JIRA now includes the new Invite Users feature. This feature lets you email invitations that allow people to sign up to your JIRA site. You just need a list of email addresses and a single click of a button.
Users receive an email message with a link to create their own account on your JIRA site.
These improvements not only help new teams, but they make adding projects and new users easier for all JIRA customers.
JIRA 5.1 Beta 1 now automatically detects the time zone of the computer you are working on. If the time zone specified in your JIRA user profile doesn't match that of the computer you are working on, JIRA will prompt you with the choice of updating your local time zone.
This is especially useful for customers who frequently travel whilst using JIRA on a regular basis.
By default, any new JIRA users will no longer be automatically notified of their own actions. Individual users can change this option through their user profile by choosing Notify me for their My Changes option when editing the Preferences section of their user profile.
You can now configure your JIRA home page, which is the page JIRA presents to you immediately after you log in.
To configure your JIRA home page, click your username's dropdown and select the appropriate home page option within the My JIRA Home section.
GreenHopper users can take advantage of this feature by selecting Agile from the My JIRA Home section. Upon selecting this option, you will be taken directly to your default GreenHopper Agile page upon logging in to JIRA.
JIRA administrators can choose between whether their users specify either a Gravatar or a JIRA-specific avatar through their user profile.
The Gravatar support feature can be activated by switching the Use Gravatar for user avatars option to ON through the General Configuration page.