33
1,217
Customers have installed this app in at least 1,217 active instances.
1,217
Customers have installed this app in at least 1,217 active instances.

    Scroll Versions for Confluence

    by K15t Software GmbHAtlassian Verified
    K15t Software GmbH is an Atlassian Verified vendor. Verified vendors demonstrate Atlassian standards for app quality, reliability, and support.

    Learn more

    for Confluence Server 6.0.1 - 6.10.1 and more versions
    Versions available for Confluence Server 4.2 - 5.10.9
    Unsupported
    This app isn't formally supported.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Supported
    K15t Software GmbH supports this app.

    Get support

    Data Center
    This app is compatible with the clustering and high-availability capabilities of our products.
    Supported
    K15t Software GmbH supports this app.

    Get support

    Data Center
    This app is compatible with the clustering and high-availability capabilities of our products.

    Plan, author, manage, and release documentation directly from Confluence and keep pace with feature-rich, fast-changing products

    Plan, author, manage, and release documentation directly from Confluence and keep pace with feature-rich, fast-changing products

    Plan, author, manage, and release documentation directly from Confluence and keep pace with feature-rich, fast-changing products

    Multiple versions

    Multiple variants

    Duplicate page titles

    With Scroll Versions you can manage and author multiple versions of your documentation in a single space. Add or update pages and publish the appropriate version when the product is released.

    Manage different product variants in a single space in a simple and logical way. Space Admins can define variants on the space level, and Authors can define which content applies to which variant.

    Use duplicate page titles within a single space. Links are kept independent of page titles, allowing renaming of pages without breaking links.

    Multiple versions

    Multiple variants

    Duplicate page titles

    With Scroll Versions you can manage and author multiple versions of your documentation in a single space. Add or update pages and publish the appropriate version when the product is released.

    Manage different product variants in a single space in a simple and logical way. Space Admins can define variants on the space level, and Authors can define which content applies to which variant.

    Use duplicate page titles within a single space. Links are kept independent of page titles, allowing renaming of pages without breaking links.

    More details

    Scroll Versions is the engine that powers great documentation. It takes management, authoring, and publishing in Confluence to new levels of ease and flexibility. Scroll Versions adds functionality for version management, variant management, permalinks (including duplicate page titles), enhanced content re-use, support for context-sensitive help, and much more.

    Key benefits:

    • Manage multiple versions in a single space
    • Use variants to set display conditions
    • Set edit permissions by version
    • Pick and choose which modules you want to use

    Watch a crash course video

    Learn more benefits of Scroll Versions

    More details

    Scroll Versions is the engine that powers great documentation. It takes management, authoring, and publishing in Confluence to new levels of ease and flexibility. Scroll Versions adds functionality for version management, variant management, permalinks (including duplicate page titles), enhanced content re-use, support for context-sensitive help, and much more.

    Key benefits:

    • Manage multiple versions in a single space
    • Use variants to set display conditions
    • Set edit permissions by version
    • Pick and choose which modules you want to use

    Watch a crash course video

    Learn more benefits of Scroll Versions

    Reviews for cloud

    (33)
    Sign in to write a review
    by Wybe Minnebo on 2017-08-17
    A big part of our documentation is generated from code and pushed to Confluence using the REST API. Documents created over REST, or updated over REST, are not versioned. Although a REST API specifically for Scroll Versions is not officially supported, K15t's support staff replied promptly and elaborately. With their help I've managed to automate the versioning of our documentation and solve a crucial problem for us. I can recommend both the add-on and the service K15t provides to anyone looking to version Confluence pages.
    0 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Ricardo Groß on 2016-12-18
    When will you support Confluence 6.0? As well as for Scroll Translations?
    0 out of 1 found this review helpful
    Was this review helpful?YesNo
    K15t Software GmbH

    Hi Ricardo-

    Would you consider removing or updating your review, since this issue has been long since solved? Thank you very much.

    -Davin (K15t Software)

    by Sylvia Barron on 2016-12-05
    This is a great tool to improve content management in Confluence. Easy to use and very helpful. Works great with Scroll Translations and Scroll Viewport.
    0 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Matt Reiner on 2016-06-09
    My company has moved from a DITA-based user guide for our application to authoring it in Confluence. When we first started in Confluence, it became painfully clear that it did not offer the versioning or publishing abilities we needed, which lead to tons of rework when trying to deploy content to a Preview and GA space. We decided to give Scroll Versions a try, and I guess I can't really state just how much it has changed things for us. Our writing team can now just pick the version in which they want content to appear and then start writing. It's a fundamental change for us, and allows us to maintain multiple versions with ease. We can now maintain a version of content for each sprints work, and publish it at the end of each sprint as we release that work. I look like a super star because our writing team can publish new content and fixes with the push a button. It's helped build trust in the team and the process. Though not a specific feature of Scroll Versions, we've used the recommended approach of building an Include Library to hold our reusable content. We've built our Include Library to several hundred pages and it's still growing. Our content is now very organized, and is being reused in multiple ways. We're even considering opening the library to other teams in the company to let use the chunks of content that's already been written for their resources. With the switch from DITA to Confluence + Scroll Versions, we've drastically increased the amount of content written each sprint, shortened review time, and removed the need for technical resources in reviewing and publishing content. This has let us focus on improving our content rather than fighting with the content creation and publishing tools.
    4 out of 4 found this review helpful
    Was this review helpful?YesNo
    by Martin Kellner on 2016-01-21
    We are using scroll versions+translation for a about two years now. There are important issues that have not been fixed until now: - Include page doesn't work anymore when using scroll translations. So reusing content from other spaces is not possible. Not acceptable workaround: put your content in one space and use variants. - Excerpt include doesn't work anymore. E.g. describing an API and quoting the key functionality from the individual function description in a table (as an overview) can't be automated and has do be done manually. - copy/move pages to other spaces doesn't work anymore. Content has to me moved or copied by cut/copy/paste - The integrated workflow doesn't protect a page from being changed after the page is already in the state "complete". Changing content in this state doesn't switch the page state to "draft" again. So you might publish content that was not reviewed. Not acceptable workaround: buy another plugin for workflow management. - Comments get lost when creating and editing a new version of a space: create a version 1, create a page, comment to this page. Create version 2, edit the page --> The comments are not copied. You don't see the comments. The issue occurs for all kind of comments (inline and bottom). - Documentation still covers version 2.x 6 weeks after the 3.x major release.
    6 out of 6 found this review helpful
    Was this review helpful?YesNo
    K15t Software GmbH

    Hi Martin,

    Thank you for giving such detailed feedback and for being a long-time customer.

    In 2015 we had about 19 releases of Scroll Versions related to new features, improvements and bug fixes. I am really sorry that the issues you mentioned were not part of those releases.

    We are aware that your example of content re-use is a key feature required for technical communication and it is currently a high priority in our roadmap.

    I am happy to get in touch with you personally if you like, to discuss/explain issues in more detail and see what we can do to help your situation.

    Cheers, Tobias (Product Manager)

    Read more reviews

    Reviews for server

    (33)
    Sign in to write a review
    by Sandra Hernández on 2018-04-16
    The evaluation is positive so far, however we have presented unwanted situations when we use add-ons from other providers that are not supported when using scrollversion, therefore we must know the impact that means changing our documentation and what alternatives we have. Thank you
    Was this review helpful?YesNo
    K15t Software GmbH

    Hi Sandra,

    Thank you for your review and we’re sorry to hear that you’re running into some issues with third-party apps. We do provide versions-compatible alternatives of the macros that are necessary for documentation authoring spaces, but there may be some that aren’t covered. Here is an article about our macro compatibility for reference and may provide some of the alternatives you’re seeking.

    Cheers,

    Shannon

    by Wybe Minnebo on 2017-08-17
    A big part of our documentation is generated from code and pushed to Confluence using the REST API. Documents created over REST, or updated over REST, are not versioned. Although a REST API specifically for Scroll Versions is not officially supported, K15t's support staff replied promptly and elaborately. With their help I've managed to automate the versioning of our documentation and solve a crucial problem for us. I can recommend both the add-on and the service K15t provides to anyone looking to version Confluence pages.
    0 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Ricardo Groß on 2016-12-18
    When will you support Confluence 6.0? As well as for Scroll Translations?
    0 out of 1 found this review helpful
    Was this review helpful?YesNo
    K15t Software GmbH

    Hi Ricardo-

    Would you consider removing or updating your review, since this issue has been long since solved? Thank you very much.

    -Davin (K15t Software)

    by Sylvia Barron on 2016-12-05
    This is a great tool to improve content management in Confluence. Easy to use and very helpful. Works great with Scroll Translations and Scroll Viewport.
    0 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Matt Reiner on 2016-06-09
    My company has moved from a DITA-based user guide for our application to authoring it in Confluence. When we first started in Confluence, it became painfully clear that it did not offer the versioning or publishing abilities we needed, which lead to tons of rework when trying to deploy content to a Preview and GA space. We decided to give Scroll Versions a try, and I guess I can't really state just how much it has changed things for us. Our writing team can now just pick the version in which they want content to appear and then start writing. It's a fundamental change for us, and allows us to maintain multiple versions with ease. We can now maintain a version of content for each sprints work, and publish it at the end of each sprint as we release that work. I look like a super star because our writing team can publish new content and fixes with the push a button. It's helped build trust in the team and the process. Though not a specific feature of Scroll Versions, we've used the recommended approach of building an Include Library to hold our reusable content. We've built our Include Library to several hundred pages and it's still growing. Our content is now very organized, and is being reused in multiple ways. We're even considering opening the library to other teams in the company to let use the chunks of content that's already been written for their resources. With the switch from DITA to Confluence + Scroll Versions, we've drastically increased the amount of content written each sprint, shortened review time, and removed the need for technical resources in reviewing and publishing content. This has let us focus on improving our content rather than fighting with the content creation and publishing tools.
    4 out of 4 found this review helpful
    Was this review helpful?YesNo
    Read more reviews

    Reviews for Data Center

    (33)
    Sign in to write a review
    by Wybe Minnebo on 2017-08-17
    A big part of our documentation is generated from code and pushed to Confluence using the REST API. Documents created over REST, or updated over REST, are not versioned. Although a REST API specifically for Scroll Versions is not officially supported, K15t's support staff replied promptly and elaborately. With their help I've managed to automate the versioning of our documentation and solve a crucial problem for us. I can recommend both the add-on and the service K15t provides to anyone looking to version Confluence pages.
    0 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Ricardo Groß on 2016-12-18
    When will you support Confluence 6.0? As well as for Scroll Translations?
    0 out of 1 found this review helpful
    Was this review helpful?YesNo
    K15t Software GmbH

    Hi Ricardo-

    Would you consider removing or updating your review, since this issue has been long since solved? Thank you very much.

    -Davin (K15t Software)

    by Sylvia Barron on 2016-12-05
    This is a great tool to improve content management in Confluence. Easy to use and very helpful. Works great with Scroll Translations and Scroll Viewport.
    0 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Matt Reiner on 2016-06-09
    My company has moved from a DITA-based user guide for our application to authoring it in Confluence. When we first started in Confluence, it became painfully clear that it did not offer the versioning or publishing abilities we needed, which lead to tons of rework when trying to deploy content to a Preview and GA space. We decided to give Scroll Versions a try, and I guess I can't really state just how much it has changed things for us. Our writing team can now just pick the version in which they want content to appear and then start writing. It's a fundamental change for us, and allows us to maintain multiple versions with ease. We can now maintain a version of content for each sprints work, and publish it at the end of each sprint as we release that work. I look like a super star because our writing team can publish new content and fixes with the push a button. It's helped build trust in the team and the process. Though not a specific feature of Scroll Versions, we've used the recommended approach of building an Include Library to hold our reusable content. We've built our Include Library to several hundred pages and it's still growing. Our content is now very organized, and is being reused in multiple ways. We're even considering opening the library to other teams in the company to let use the chunks of content that's already been written for their resources. With the switch from DITA to Confluence + Scroll Versions, we've drastically increased the amount of content written each sprint, shortened review time, and removed the need for technical resources in reviewing and publishing content. This has let us focus on improving our content rather than fighting with the content creation and publishing tools.
    4 out of 4 found this review helpful
    Was this review helpful?YesNo
    by Martin Kellner on 2016-01-21
    We are using scroll versions+translation for a about two years now. There are important issues that have not been fixed until now: - Include page doesn't work anymore when using scroll translations. So reusing content from other spaces is not possible. Not acceptable workaround: put your content in one space and use variants. - Excerpt include doesn't work anymore. E.g. describing an API and quoting the key functionality from the individual function description in a table (as an overview) can't be automated and has do be done manually. - copy/move pages to other spaces doesn't work anymore. Content has to me moved or copied by cut/copy/paste - The integrated workflow doesn't protect a page from being changed after the page is already in the state "complete". Changing content in this state doesn't switch the page state to "draft" again. So you might publish content that was not reviewed. Not acceptable workaround: buy another plugin for workflow management. - Comments get lost when creating and editing a new version of a space: create a version 1, create a page, comment to this page. Create version 2, edit the page --> The comments are not copied. You don't see the comments. The issue occurs for all kind of comments (inline and bottom). - Documentation still covers version 2.x 6 weeks after the 3.x major release.
    6 out of 6 found this review helpful
    Was this review helpful?YesNo
    K15t Software GmbH

    Hi Martin,

    Thank you for giving such detailed feedback and for being a long-time customer.

    In 2015 we had about 19 releases of Scroll Versions related to new features, improvements and bug fixes. I am really sorry that the issues you mentioned were not part of those releases.

    We are aware that your example of content re-use is a key feature required for technical communication and it is currently a high priority in our roadmap.

    I am happy to get in touch with you personally if you like, to discuss/explain issues in more detail and see what we can do to help your situation.

    Cheers, Tobias (Product Manager)

    Read more reviews

    Pricing

    10 users$30025 users$60050 users$1200100 users$1900250 users$3200500 & upAdditional pricing details
    10 users$300/year25 users$600/year50 users$1200/year100 users$1900/year250 users$3200/year500 & upAdditional pricing details

    Paid-via-Atlassian pricing FAQ

    How does server app pricing work?

    Server products and apps are hosted on your servers. Licenses are perpetual and the purchase price include 12 months of maintenance (support and version updates).

    You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your host product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

    How do I determine my server pricing?

    Apps are billed based on the number of users in your host product. The app tier should match the licensed user tier of the Atlassian host product. For example, if you have a Confluence Server license for 25 users, you should purchase the 25-user tier for apps. Even if fewer users want to use the app than your host product license, the two licenses should match exactly.

    Do you offer academic, community, or open-source licenses?

    For server apps, purchase and renewal is half-price if you have an academic license for your Atlassian host product. Server apps are always free for community and open-source licenses.

    For more details about qualifying for special licenses, see here.

    Can I extend my free trial?

    For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian host product, and you're all set.

    How can I buy apps for my legacy Jira Server or Confluence Server license?

    If you own a legacy Jira Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:

    • Purchase the app at the non-legacy Unlimited (10000+ users) tier.
    • Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.

    Learn more

    Paid-via-Atlassian pricing FAQ

    How does Data Center app pricing work?

    Data Center pricing FAQ

    If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

    How do I determine my Data Center pricing?

    Data Center pricing FAQ

    Do you offer academic, community, or open-source licenses?

    Data Center pricing FAQ

    Can I extend my free trial?

    Data Center pricing FAQ

    K15t Software GmbH is an Atlassian Verified vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.

    K15t Software GmbH is an Atlassian Verified vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.

    Vendor support resources

    Documentation

    Find out how this app works.

    Wiki

    Collaborative documentation platform hosted by this vendor.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this app.

    Vendor support resources

    Documentation

    Find out how this app works.

    Wiki

    Collaborative documentation platform hosted by this vendor.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this app.

    Versions

    Version 3.9.0 • Confluence Server 6.0.1 - 6.10.1 • Released 2018-07-02

    Summary

    Visual improvements; changes to integration with Viewport; bug fixes

    Details

    Major change

    • hiding a version does no longer hide it in Viewport
    • it's no longer possible to create new versions with names that have more than 80 characters

    UI Improvements

    • byline view
    • toolbar labels and order
    • reports are now pre-filled with the current working version
    • users can now use tabs to navigate through UI dialogues
    • theme integration is now more robust to cope with non-existing themes
    • Include Plus macro dialogue does no longer consider selected previously variant

    Fixed

    • Spaces with Page Properties hang if Page Properties report was used in _SVContentFooter page
    • Page Properties report macro doesn't show anything when _SVContentFooter is defined in a space
    • Byline moves on top of the content when making a browser window small or zooming in
    • users were able to assign empty page keys
    • variants pop-up does not update correctly after changing variants of a page

    Read the full Scroll Versions 3.9.0 release notes

    Versions

    Version 3.9.0 • Confluence Data Center 6.0.1 - 6.10.1 • Released 2018-07-02

    Summary

    Visual improvements; changes to integration with Viewport; bug fixes

    Details

    Major change

    • hiding a version does no longer hide it in Viewport
    • it's no longer possible to create new versions with names that have more than 80 characters

    UI Improvements

    • byline view
    • toolbar labels and order
    • reports are now pre-filled with the current working version
    • users can now use tabs to navigate through UI dialogues
    • theme integration is now more robust to cope with non-existing themes
    • Include Plus macro dialogue does no longer consider selected previously variant

    Fixed

    • Spaces with Page Properties hang if Page Properties report was used in _SVContentFooter page
    • Page Properties report macro doesn't show anything when _SVContentFooter is defined in a space
    • Byline moves on top of the content when making a browser window small or zooming in
    • users were able to assign empty page keys
    • variants pop-up does not update correctly after changing variants of a page

    Read the full Scroll Versions 3.9.0 release notes

    Installation

    1. Log into your Confluence instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Scroll Versions for Confluence via search. The appropriate app version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Scroll Versions for Confluence. You're prompted to log into MyAtlassian. Scroll Versions for Confluence begins to download.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Confluence instance.

    To find older Scroll Versions for Confluence versions compatible with your instance, you can look through our version history page.

    1. Log into your Confluence instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Scroll Versions for Confluence via search. The appropriate app version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Scroll Versions for Confluence. You're prompted to log into MyAtlassian. Scroll Versions for Confluence begins to download.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Confluence instance.

    To find older Scroll Versions for Confluence versions compatible with your instance, you can look through our version history page.

    Similar apps