Documentation for JIRA 6.4 EAP. Not using this? See below:
(JIRA 6.3.x documentation | JIRA Cloud documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

31 March 2011

JIRA 4.4 EAP 2 (a.k.a 4.4 milestone 2 or 'm2') is a public development release leading up to JIRA 4.4. An Early Access Preview (EAP) release is a snapshot of our work in progress, primarily focused on allowing JIRA users to see the new features in advance and provide us with some useful feedback. It also gives 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.

(info) Please note that JIRA 4.4 EAP 1 was not released to the public.

While development work on JIRA 4.4 commenced relatively recently, we want your involvement from the earliest days. Please provide feedback here.

JIRA 4.4 brings you a visual Workflow Designer and Workflow Viewer. We are also very pleased to announce that the JIRA installation process has been improved and simplified.

Highlights of JIRA 4.4 EAP 2:

Thank you for your interest in JIRA 4.4 EAP 2
Download EAP

Upgrading to JIRA 4.4 EAP 2

JIRA EAP releases are available here. When upgrading, please follow the JIRA 4.4 Upgrade Notes.

Do not use in production

  • EAP releases are not safe — EAP releases are snapshots of the ongoing JIRA development process. As such:
    • While we try to keep these releases stable, they have not undergone the same degree of testing as a full release.
    • Features in development releases may be incomplete, or may change or be removed before the next full release.
  • No upgrade path — Because EAP releases represent work in progress, we can not provide a supported upgrade path between EAP releases, or from any EAP to the eventual final release. Thus, any data you store in a JIRA EAP release may not be able to be migrated to a future JIRA release.

Highlights of JIRA 4.4 EAP 2


Visual Workflow Designer For Administrators

JIRA 4.4 provides a visual representation of your workflow, making it easy to map out your business processes.

Simply go to "Workflows" in JIRA administration as usual, and click the "Design" link for the workflow you wish to edit. You can right-click on individual Steps and Transitions to view more information.



Workflow Viewer on the "View Issue" Screen

You can also see a read-only view of the workflow from the "View Issue" page — just select "View Workflow" from the "More Actions" menu. We've made it simple for everyone to use, without requiring Flash to be installed.

The workflow viewer also highlights the current status of your issue in the workflow.



Database Connection Now Included In Setup

In JIRA 4.4, connecting to an external database is now part of the standard setup wizard. It will change before the final 4.4 release, but here is how it looks in M2:



Console Installer Wizard for Linux

A simple command line/console installer wizard is now available for Linux operating systems.

To install JIRA, simply download the Linux .bin installer file and at the command line or shell prompt, execute this file and follow the remaining prompts!

You can install JIRA as either the 'root' user or a non-root user under Linux. Currently, however, JIRA will be run as the same Linux user account which is used to install JIRA via this wizard. We intend to change this behaviour in a future EAP.

(minus) If you use the console installer wizard to install JIRA as the root user on your Linux operating system, then for security reasons, you should not use this JIRA installation in a public-facing environment.



Improvements to the Windows Installer Wizard

The installer wizard for Windows now works smoothly for Windows 7 and Vista.

The process for installing JIRA as a Windows service has also improved and wizard now allows you to specify the port numbers used to run and access JIRA.


Other Enhancements and Fixes

For the list of issues resolved in JIRA 4.4 so far, click here.


  • No labels


  1. I can tell you now that the workflow designer is going to be very much welcomed by many. I would like to know if this now supports common actions? Currently I am required to export the XML, modify and import where common actions are required, this process is a PITA to update existing workflows as you have to relink the scheme to the projects.

    I'll be keen to try out 4.4 this week (smile)

    1. The workflow designer does support common transitions (as well as global transitions).  You can download the existing version on that works with previous versions of JIRA if you're interested.  Glad you're excited about 4.4 (so are we)!

  2. @2. Workflow Viewer on the "View Issue" Screen

    For quite some time we use the great 'Workflow Visualization Plugin' created by Jamie Enchlin (

    Comparing this and your new approach I currently* prefer Jamies plugin:

    • Transition errors show the "Transition Names"
    • Graphic layout is highly configurable (lot of options for the dot-tool)
    • Clicking on any status or transitions directly jumps to the related workflow-admin-section.
    • Maybe you add some more options to customize this generated Workflow pic?

    Are there any plan? Comments?

    Best Regards,

    PS: The graphical workflow designer might be useful, although I'm very happy with the current table approach (and if needed the XML option).

    1. I also like the fact that Jamie's issue tab panel shows the path this issue has taken through the workflow.

    2. Markus,

      We have some similar enhancements in mind for the workflow view on the View Issue screen.  The next step we'd take with the read only diagram would be transition labels.

      Thanks for the detailed feedback, glad to know we're thinking along similar lines.



  3. Hi Dave,

    yes, sure! 100% ACK from my side.

    People like to see the path an issue has taken. AS well very usefull in Jamie'S plugin is that transitions lines get thicker if certain transitions get repeated (as well indicated by the number of rounds).

    All this features (as minimum (smile) need to be supported by the Atlassian plugin until I would deinstall Jamies's plugin. My 2 cents only.


  4. How does it handle a transition with multiple targets?