Documentation for Confluence 5.8 (Server).
Documentation for Confluence Cloud and earlier versions of Confluence is available too.

Skip to end of metadata
Go to start of metadata

Confluence 3.1 Beta 2 has been released!


Please refer to the Confluence 3.1 Beta 2 Release Notes for updated information on the enhancements available in this version.

Confluence 3.1 Beta 1 is a public development release ("Beta") leading up to the official release of Confluence 3.1, which we aim to ship in Q4/2009.

Confluence versions marked "Milestone", "Beta" or "Release Candidate" (RC) are development releases, which are preliminary releases leading up to the official release of a major Confluence version. They are a snapshot of our work in progress and provide an advance preview of new features to our customers and the general public. Confluence plugin developers can also use development releases to test and fix their plugins in advance of an official release.

The main distinction between a beta and a milestone release is that milestone releases typically acquire new features with each subsequent milestone version, whereas beta releases are predominantly feature-complete. Beta releases still undergo bug fixing and occasionally, existing features may be enhanced or added in subsequent beta versions. Release candidates are close to being ready for final release, but may still undergo changes before the final release.

Do not use in production

Development releases should not be used in production environments as they are not officially supported.

For all production use and testing of Confluence, please use the latest official release.

Who should try this out?

With development releases, the Confluence development team aims to provide plugin developers with an opportunity to see the latest changes in the code.

Furthermore, if you are a Confluence customer who is eager to see the new features and provide us with feedback on our upcoming major release, we encourage you to try out our development releases.

Please note the following

  • Development releases are not safe. Development releases are snapshots of the ongoing Confluence development process. For that reason:
    • 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 development releases represent work in progress, we cannot provide a supported upgrade path between development releases, or from any development release to the eventual final release. Thus, it is possible that you will not be able to migrate any data you store in a Confluence development release to a future Confluence release.
  • Atlassian does not provide support for development releases.

Each development release has passed all our automated tests, has undergone some performance testing and has been used for one week on our official internal Confluence server. Furthermore, most of the solved issues have been reviewed.

Be aware that our development releases are still undergoing final performance and compatibility testing for databases and application servers. Hence, we recommend that you use development releases on installations with small (as opposed to full production-level) user bases.

Upgrade Procedure

If you wish to upgrade your existing Confluence installation with this version, ensure you have created a separate copy of your current Confluence production installation first and using that copy, follow the normal upgrade instructions to upgrade it to this development release. If you have also implemented customised site- or space-specific layouts, you will need to re-implement them after the upgrade. Otherwise, some of the new features in Confluence (or possibly existing features) may not function correctly.

Downloads

All development releases are available from Development Releases on the Atlassian website.

Known Issues

There are several bugs outstanding which will be resolved before the official release. Some bugs you are most likely to come across are:

  • Page Preview — When editing a page or blog post and you click the 'Preview' tab, only the first section of content is shown. You will not be able to scroll down to view the remaining content on a page.
  • Widget Connector Icon — The current icon has not yet been finalised and will change before the official release of Confluence 3.1.
  • Quick Navigation Aid — The Quick Navigation Aid does not work in Internet Explorer 6.0.

Refer to our JIRA site for a list of Confluence 3.1-specific bugs.

Highlights of Confluence 3.1

Highlights of this Release:

Introducing Gadgets

Gadgets are small objects that offer dynamic content and functionality which may be served by any OpenSocial-compliant web application, such as JIRA 4.0+, the same or another Confluence installation, or non-Atlassian applications such as iGoogle and Gmail.

  • Confluence supports the use of gadgets in pages and blog posts, which are accessible through the macro browser.
  • Confluence can also serve its own gadgets, for use in any other OpenSocial-compliant web application including the same or another Confluence installation. Two such gadgets are bundled with Confluence:
    • Activity Stream — This gadget shows a list of recent activities that have occurred on the Confluence server, such as the addition of new pages, blog posts or comments, content edits, status updates and so on.
    • Quick Navigation Aid — This gadget provides heading and content search capabilities on a Confluence server.

Inserting a JIRA Gadget onto a Confluence Page

Office 2007 Support

Confluence now provides full support for Office 2007 files, allowing you to view and edit content from Microsoft Word 2007 (.docx and .dotx), PowerPoint 2007 (.pptx and .potx) and Excel 2007 (.xlsx) files.

  • Along with existing Microsoft Office versions, Confluence now fully indexes Microsoft Office 2007 files and their content can be searched by Confluence.
  • Office files can be edited directly from any page's or blog post's list of attachments.
  • Using Confluence's Office connector macros, you can insert Word, PowerPoint or Excel 2007 files directly into your Confluence page.

New 'Move Page' Feature

Confluence introduces a new page moving feature, that easily allows you to move the page you are currently viewing, adding or editing to another page elsewhere in the same or another space of your Confluence site. This feature is available through a new 'page move' dialog box, which provides the following flexible methods for moving pages:

  • Known Location – Allows you to type the name of a space and within that space, the 'parent' page under which to move your page.
  • Search – Allows you to search for a 'parent' page (within a selected space or set of spaces) under which to move your page.
  • Recently Viewed – Allows you to select one of your recently viewed pages to be the 'parent' of your page to be moved.
  • Browse – Allows you to select a space and page (within the tree of pages in the space) that will be the 'parent' of your page to be moved.
    For more information, refer to Move and Reorder Pages.

New Image Browser

A new 'Image Browser' has been introduced to replace the old 'Insert Image' dialog box. The image browser provides a less-cluttered and enhanced interface that allows you to:

  • Hover over any image in the browser and expand the image (to preview it in detail) by clicking its 'magnifying glass' icon in the lower-right corner, before inserting it onto a page.
  • Add a link to an image elsewhere on the web via the image's URL.

Draft Comparisons

Confluence's drafts features have been improved, such that you can now view any of your unsaved draft changes before deciding to resume editing them. This nifty feature comes in handy, particularly when other people have made subsequent changes to a page or blog post in your drafts list and you need to merge changes or resolve a conflict.

New Page Restrictions Dialog Box

Confluence's page restrictions feature has been incorporated into a convenient and accessible dialog box that is now easier to use than before.

  • The page restrictions dialog box can be accessed from the padlock icon or the 'Tools' -> 'Restrictions' menu item on any Confluence page. From this dialog box, you can view all viewing and editing restrictions associated with the page you are viewing. You no longer need to view the page's associated 'Info' page in order to view these restrictions.
  • It is no longer necessary for a page to be in edit mode in order to modify its page restrictions. You can edit all page restrictions from this dialog box.
  • The page restrictions dialog box is still accessible when when a page is in edit mode.

New Rich Text Editor Insert Menu

Confluence's rich text editor now combines a number of its commonly used editing features into a new convenient 'Insert' menu.

  • The Horizontal line, Insert Symbol and Insert Emoticon Toolbar icons have been moved into the new insert menu.
  • The functionality to insert images, links or attachments into a page can now also be accessed from this menu.
  • The macro browser, as well as a number of commonly-used macros are conveniently accessible from this menu too.

Other Editor Enhancements

Macro Browser Smart Fields

When using the Macro Browser, an 'auto-complete' feature is now provided on any parameters that require the entry of a single item, such as a page title, username or space key. This greatly facilitates the customisation of macros and minimises the need to know the exact item names in advance.

Edit Mode Exit Notification

Whenever you add or edit a page, comment or blog post and then click onto another Confluence feature that navigates away from your unsaved content, a message box appears, warning that your content will be saved as a draft (if it is a page) or lost (if a comment). This allows you to cancel out of this action if it was accidental.

Other Improvements

Other small enhancements and improvements to Confluence include:

  • Support for Internet Explorer 8 — Confluence 3.1 now fully supports Internet Explorer 8, released around mid-2009.
  • Support for OAuth — With the introduction of gadgets (above) in this release, Confluence 3.1 now allows you to establish OAuth relationships with other web applications such as JIRA 4.0+, iGoogle, Gmail etc., thereby allowing them to share resources via gadgets.
  • New 'Link to this page' feature — If you wish to link to a Confluence page from any other location on the web, use the convenient 'Link to this Page' feature (available from any page's or blog post's 'Tools' menu). Upon selecting this feature, the 'Link to this Page' dialog box opens, from which you can copy three versions of the link to embed elsewhere:
    • Link – Standard URL which should work from any other accessible location on the web.
    • Tiny Link – A reduced-length version of the 'Link', which can be used in text fields of limited length, such as tweets or Confluence Status Updates
    • Wiki Markup – A wiki markup version of the link, which can be used in any other location within your Confluence site.
  • 'More' links on activity streams — 'More' links have been added to various activity streams throughout the Confluence interface, including the profile sidebar, a user's profile page and via the recently updated macro. Clicking on a 'More' link expands the list of results, providing a convenient means of accessing progressively more distant user activities.
  • New Log In and Log Out screens.
  • In an aim to minimise confusion, 'News Items' are now consistently called 'Blog Posts' throughout the Confluence interface and a list of blog posts is collectively referred to as a 'Blog'.
  • Other minor interface improvements.
  • No labels

19 Comments

  1. Cannot proceed with upgrade. The license version is incompatible with this Confluence installation. Confluence 3.1 and above requires a new license format. Please upgrade your license or generate an evaluation license. If you have a new license, please enter it on this page and restart.

    I can't upgrade the developer license on my.atlassian.com

    Regards.

    1. Hi Tim,

      When viewing your developer license on my.atlassian.com you should see the following appear below your license key:

      If you do not see this, or the "update" link does not work for you, please send an email to dave at atlassian dot com with more details of the problem and we'll help you as soon as we can.

      We have attempted to upgrade the license for you, but did not find a developer license to your name.

      Cheers,
      Dave

  2. Safari 4 WYSIWYG support isn't mentioned in the release notes, nor RTE for Chrome.  I'm certainly more excited about these browsers than IE8. 

    According to the related bugs, support for these browsers is on track for 3.1:

    http://jira.atlassian.com/browse/CONF-16079

    http://jira.atlassian.com/browse/CONF-12952

  3. What about http://jira.atlassian.com/browse/CONF-12319? It's been open for 16 months and promised in several previous releases.

    thanks,
    Igor

    1. We will be putting together a developer taskforce for discussing ideas around user management later this month (and for implementing these ideas of course), but that work will obviously not make it into 3.1. We will get in touch with the customers who have urgent needs around UM, and of course we won't forget you!  No promise that this particular issue will get adressed though. Let's keep the discussion on that issue for now. This page is for 3.1 specific feedback. (smile)

  4. Anonymous

    We re looking forward to this release.

    Wish list:  Would have  loves to see some enhancments to the Socialisation features at any level but I guess this will have to wait.

    Good Beta!

  5. I love what you guys are doing in general, and I like how 3.0 is faster and more stable.

    However, I have to ask - what about Sectional Editing:

    http://jira.atlassian.com/browse/CONF-5913

    As you're aware, it's the 6th most highly voted improvement.

    Being a product manager, I understand that votes are far from the best indicator of necessity or urgency.  But I believe it would be a very important improvement to confluence which will allow both:

    • Casual users to get into it easier
    • Make power-users able to manage much larger documents

    As it is, with large docs, my collaborators balk at being able to make changes.  With sectional editing being easy, I think I could entrench confluence with more users across my organization.

    Interested to hear your thoughts on your plans for this (even if it's not soon, just an idea of what your plans are).
    Thanks.

    1. Hi Ilia,

      while not exactly 3.1 specific feedback either, let me quickly try to explain: We are keen on doing sectional editing too (we have long documents on our Confluence servers as well...), but it will take a while till we get there. We are looking into doing some groundwork for this feature over the next few months, but the feature itself definitely not scheduled yet, and I can't give you any timeline either.

      Anyway, what do you think about the other editing improvements in 3.1 though? Any feedback on the new editor dialogs for example?

  6. Anonymous

    Smartfields are a great new feature, are they associated with a new type so that the macro browser can differentiate between a parameter requesting a page title, username, spacekey, and a standard string?

    1. Pretty much! When we first created the macro browser we added different types that could be given to parameters, even though the parameter would still get treated as a string in the UI.

      With smart fields we've simply started rolling out JavaScript to handle some of the types differently in the UI. Currently the smart fields handle the types "username", "spacekey", "confluence-content" (for page titles with optional spaces in the standard form SPACE:Title) and "attachment".

  7. Anonymous

    For those that are concerned about long-standing UM deficiencies and other enterprise scale issues, remember that Atlassian defines user "votes" using a 'one person, one vote' model.  There's no accounting for the size of organization (number of users) licensed by each voter.  In practice, this means that the needs of those with large deployments are dramatically underrepresented, while those with smaller deployments are overrepresented.   This is great for those of us running small shops as we get a top-notch development team willing to make a series of feature tradeoffs, all generally in our favor.

    But this also means that Confluence has little chance of evolving into a serious enterprise-scale solution -- for at least the next year, possibly longer The inherent biases of the current voting system are strategically driving the whole business towards serving the needs of the "small accounts" rather than the "large accounts".  The bet Atlassian is (unconsciously?) making through the "one person, one vote" approach is that they can build a bigger business by selling into a large number of small accounts vs. a much smaller number of larg accounts. 

    1. Dear anonymous, you should really have a look at our guidelines on how we choose to work on new features , because I think you have gotten an entirely wrong impression of how we work with votes at Atlassian. Votes are just one out of many factors. Example: All the performance work we did for the previous 3.0 version for example (and heaps of security model work) were done entirely for enterprise customers, even though there was no single issue with many votes for it. We are currently looking into user management improvements (actually, infrastructure work has already started), and have a few other enteprise-y items on our backlog as well. Some of the 3.1 features (like Office2007 and Page-Move improvements) were particularly demanded by large organisations too, and while they had a fair share of votes, this was again just one of several factors in our decision making process.

  8. I get an error when trying to register a gadget. I'm using the Mac eval installer if that has anything to do with it. See JIRA ticket CONF-17640 for details.

    1. Got exactly the same with the Mac Eval Installer.  Works fine with standalone ZIP installer on Mac.

  9. We are really looking forward to Office 2007 support in 3.1 Is there an easy way to see all bug fixes and feature additions for 3.1?

    1. Hi John,

      there is currently not yet a simple way to see all bugs fixed, we will be cleaning up our JIRA project in about two weeks and then provide the links. Right you can browse the project at http://jira.atlassian.com/browse/CONF, but there are for example quite a few bugs that occurred only during the development phase, and which are not relevant to external parties (but which are important to our partners and plugin developers to know about). Also, the issues are split up into our milestones and beta releases, which is important for us internally right now, but which we will clean up as well soon once the release has been shipped.

      The features are listed above, but we will go into more details with the Beta 2 notes, and provide official feature release notes when the final version ships.

  10. This looks really good. For our organization, the Word 2007 support is probably the most awaited feature. A question on the New Image Browser: the alternative "From the Web", I suspect that it does what it sounds like it does, but out of curiosity: does it include finding graphics attached to other pages/spaces in your Confluence installation? Or do I still have to enter a graphic link such as this manually, even if the graphic is in the page "next to the one" I am working on?

    Keep up the good work!

    /Lars

    1. Unfortunately, we didn't get around to implementing that feature. It would have been one of the next items on the roadmap, but time's up.

  11. Our organisation recently started using Confluence and these features will fix some of the real issues I have had with deployment as your average user has real difficulties understanding that 2007 format is a no go. So great to see. Going to install the beta to see how it performs the 2007 and office connector stuff. But in the meantime one thought.

    On the revised image browser, will the image grabber applet still be functioning as this is critical to us in preparing instruction documents.

    Regards