Issues Resolved in Confluence 3.3
Confluence 3.3 Release Notes
On this page
Related content
- Configuring build results expiry for a plan
- How to archive Bamboo project, plans or deployment projects
- Deleting the results of a plan build
- Artifacts in Bamboo Server
- How to find historical deployment records in Bamboo
- Bamboo fails with "No space left on device" due to large artifacts
- How to migrate a Bamboo instance with a large number of artifacts and build logs
- Deleting a job's current working files
- Disk space hotspots and cleanup best practices in Bamboo
- Disabling or deleting a job
Below are the top 100 issues resolved in Confluence 3.3, ordered by number of votes. For the full list of the fixes, improvements and new features, please take a look at our issue tracker. Please also take a look at the Confluence 3.3 Release Notes for the new features in Confluence 3.3.
type | key | summary | status | resolution | votes |
---|---|---|---|---|---|
Unable to locate Jira server for this macro. It may be due to Application Link configuration. |
Above are the issues resolved in Confluence 3.3, ordered by number of votes. For the full details of the fixes, improvements and new features, please take a look at our issue tracker.
Last modified on Sep 13, 2013
Related content
- Configuring build results expiry for a plan
- How to archive Bamboo project, plans or deployment projects
- Deleting the results of a plan build
- Artifacts in Bamboo Server
- How to find historical deployment records in Bamboo
- Bamboo fails with "No space left on device" due to large artifacts
- How to migrate a Bamboo instance with a large number of artifacts and build logs
- Deleting a job's current working files
- Disk space hotspots and cleanup best practices in Bamboo
- Disabling or deleting a job
Powered by Confluence and Scroll Viewport.