Even though it's a "minor" upgrade it introduces a bunch of great new features, both for users, project administrators and JIRA administrators.
Installation
Installing and upgrading JIRA standalone has always been easy but the new installer and configuration wizard really make it trivial.
If you're going to perform a new JIRA installation, the installer now takes care of everything, including the creation of a dedicated JIRA user to the registration of JIRA as a service in the operating system. The new configuration wizard lets you configure the external database used by JIRA (are you using one, aren't you?) with a handy graphical user interface just during the installation phase. Now, manual configuration file editing and JIRA restarts are left to the geeky administrators.
If you're going to perform multiple JIRA installation, you're going to like the new unattended installation mode that brings even more enterprise-like features to JIRA. Administrators can specify installations settings for JIRA in a dedicated file that can be fed to the installer. To make things even simpler, the JIRA installer is creating one for you when you perform an interactive installation. Just take it and use it as a template: apply the modifications you need and feed it to the installer.
If you're going to perform a JIRA update, something which is very common giving the pace at which Atlassian releases JIRA updates, life's never been so easy. The installer has an update option that takes care of everything, from the backup of your JIRA home directory to the migration of the most common settings (such as web server configuration and database configuration).
User Interface Improvements
JIRA v. 4.4 introduces plenty of improvements targeted at users.User Time Zone
If users of a single JIRA instance of yours are scattered around the globe, you're going to appreciate the new User time zone property of the user profile. Users can now specify the time zone they're working on so that other people can now what to expect when interacting with them.
User Time Zone |
Workflow Viewer
Users granted the appropriate privilege can now see the current status of an issue in a workflow viewer. Users are now able to quickly and visually identify where an issue is in the workflow.
JIRA Workflow Viewer |
Other Improvements
There are many other improvements available, such as:
- New mobile-friendly email templates.
- New defaults fields in workflow transition screen, such as Linked Issue.
- Multiple file selection when uploading attachments.
- JQL improvements.
- Refurbished Activity Stream gadget.
Please read the official JIRA Release Notes for further information about this version or download a copy of JIRA and try it now.
Improvements for the Administrators
JIRA v. 4.4 introduces many interesting new features that aim to ease further the administration of JIRA and JIRA projects. The thing I like most is that Atlassian has succeeded in simplifying considerably the administration JIRA interface without losing any of the legendary JIRA configuration flexibility.
New Administration Mode
The new administration mode replaces the old administration window and its large administration panel on the left side of the window. The administrator can now enter the administration mode and use a totally new user interface. The administration mode welcomes the admin with a new dashboard-like control panel, where links to the administration windows are grouped by subject.
I really feel that this new mode, beyond the eye candy of the new windows, provides a feeling of order and clarity that the old administration window was losing over time under the weight of more and more menu items.
Workflow Designer
This is a groundbreaking feature many, many administrators are going to love. Simply.
Up to JIRA 4.3, administrators had to define workflows on tabular views, defining the states of the finite state machine and the transaction between them. Looking at a workflow was not possible, the only way being using pencil and paper to draw the finite state machine. The configuration was somewhat cumbersome, although quite clear with respect to other implementations I've seen.
With JIRA 4.4, administrators can now define a workflow using a graphical user interface. Drawing the state machine has never been so easy and I expect that workflow implementation and maintenance costs are going to fall heavily with this new tool.
JIRA Workflow Designer |
Improved Project-Centric Administration
JIRA powerful and flexible configuration features always come with some costs: administrators had to fully understand what JIRA schemes are and how they are supposed to be used. The old JIRA configuration interface was schema-centric and sometimes it could be difficult to easily grasp which scheme was supposed to be changed to apply the desired configuration in a project.
Things have changed with JIRA 4.4. The new JIRA configuration interface is project-centric: it combines the power provided by JIRA schemes with an easy user interface that helps the administrator perform his tasks, guiding him through the various configuration steps, always starting from a project administration window.
Conclusions
In my opinion, this is one of the biggest JIRA updates in the recent years. If you think that this is just a minor upgrade, I'm sure you'd be surprised to discover that you're wrong: maybe such an upgrade would have deserved a major version upgrade.
Impressions were overall good. I was pleased to discover that I had not to go through diff-ing configuration files to migrate the Tomcat and database configuration from the old to the new JIRA instance: not only the odds of making a mistake are dumped to zero, but the already short time required to update JIRA has been almost zeroed as well.
Both users and admins are going to love the new features introduced with this versions. I sincerely expect that administrators productivity is going to increase, as well as their "disposition" to accept user customization requests for their projects. Customizing JIRA has never been so easy and the new designer brings a totally new way to define new workflows and maintain existing ones.
That's pretty more to it than this, and the best thing you can do is do a JIRA test drive yourself. Here are the complete JIRA 4.4 Release Notes and here's where you can download JIRA and try it yourself.
Our email outgoing stopped working after upgrading to JIRA 4.4.
ReplyDeleteWe use Google Apps as our email host. (with SSL). The error it show is in the trail.
Please assist. How to make email start working.
Tejas
India
Partial error message is............
An error has occurred with sending the test email:
com.atlassian.mail.MailException: javax.naming.NameNotFoundException: Name mail is not bound in this Context
at com.atlassian.mail.server.impl.SMTPMailServerImpl.send(SMTPMailServerImpl.java:175)
at com.atlassian.jira.web.action.admin.mail.SendTestMail.doExecute(SendTestMail.java:93)
at webwork.action.ActionSupport.execute(ActionSupport.java:165)
at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:76)
at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:39)
at webwork.interceptor.NestedInterceptorChain.proceed(NestedInterceptorChain.java:31)
at webwork.interceptor.ChainedInterceptor.intercept(ChainedInterceptor.java:16)
at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:35)
at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:205)
at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:143)
I upgraded several JIRA instances with configurations similar to yours (Google Apps STMP server) I haven't experienced any problem so far.
ReplyDeleteI suggest you use Atlassian support (if you're entitled) or post your question to Atlassian forums at http://forums.atlassian.com/index.jspa.