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

29 November 2010

Confluence 3.4.3 is a bug-fix release. The list of fixes is at the bottom of this page.

In addition to releasing Confluence 3.4.3, we have also updated the code for the Expand user macro so that the body of the macro now visible in PDF exports. To take advantage of this improvement, please copy the macro 'template' from this documentation page: Writing the Expand User Macro. Note that you do not need to upgrade to Confluence 3.4.3 in order to use the updated macro. Simply updating your macro template is enough.

Don't have Confluence 3.4 yet?

Take a look at the new features and other highlights in the Confluence 3.4 Release Notes.

Release Notices

Upgrading from a previous version of Confluence should be fairly straightforward. Please read the Confluence 3.4.3 Upgrade Notes. We strongly recommend that you back up your confluence.home directory and database before upgrading.

Updates and Fixes in this Release


  • No labels


  1. The Fixed Issues list should not be showing issues marked as 'Duplicate' or 'Won't Fix'.

      1. I didn't see this before it was fixed. But I want to make sure it was fixed right.
        Issues resolved as Duplicate and Won't Fix shouldn't have a fixversion.

        1. I just changed the JQL to query on "resolution = Fixed" instead of "status in (resolved, closed)"

          1. Ah, I think we need to show the closed issues.

            1. Okay. I just reverted back to Sarah's page with the original query and then edited the two offending issues to remove the fix version.

              1. Heh, I went to look what the issues are, wrote the below comment, and then discovered the fixversions had disappeared.

            2. That will show closed issues. So Bill's fix will display the correct issues.

              My point is that the old query should also have shown the correct issues, since we don't usually put a fixversion on duplicates or won't fixes. Per used to grump at people for doing so regularly. I don't know why he thought it was important but I do agree that it seems wrong to put a fixversion on things that don't have resolutions of fixed.

              1. With the new Scrum process, the fix version is automatically added when using the GH planning board for any issues that are scheduled to be looked at during the sprint. If the resolution for any of those issues is Won't Fix or Duplicate, then the fix version will remain unless the developer remembers to manually remove it.

                If we do still think it is important, then we need to find a better way of doing this, as it I'd guess it will happen more frequently. My opinion is that we shouldn't worry about it, and just change the query to exclude such issues.

                1. My opinion is that we shouldn't worry about it, and just change the query to exclude such issues.

                  I tend to agree. I don't know why it was such a big deal to Per.