FAQ

Projects typically accumulate a wealth of documents. From workflow documentation, to roadmaps, to shared credentials. All of these need to go somewhere. So, why not put them where your team has to go already, right in Jira. This way users that need them can easily get to them without having to remember yet another url, or manage the separation between project docs and JIRA issues.

Simple Wiki allows you to do all of that, without the need to add another server for confluence, or manage another tool somewhere else.

As an added bonus, SimpleWiki integrates with JIRA, and thus you can easily mention users, link to Issues, and so forth.

Well, that largely depends on what you're trying to do, how deep your your pockets are, and how much time and effort you want to spend in managing another server/product.

Simple Wiki is meant to be a lightweight but feature rich alternative to Confluence. Our aim is to provide a way to manage content relevant to your issues, teams, and processes right inside of Jira. Our pages are lightweight, and support most of the functionality you would need for 'Simple' documentation.

The fact that Simple Wiki runs right inside of Jira itself means you don't need to manage a separate server, and your content is automatically part of the Jira instance (and its backup procedures, etc). It also means that from the moment you install it, it is ready to go, with no further configuration or integration necessary.

Confluence is a behemoth with a long development history, huge team, and even bigger budget and a fantastic ecosystem of vendors and developers behind it.

Quite frankly, we can't really compete with the full Confluence experience. If that's what you're looking for, you might not want Simple Wiki instead of Confluence.

On the other hand, sometimes Confluence can be big and heavy and require a bit of a learning curve.

Yes. You can find it here:

Yes. You can find it here:

The SimpleWiki plugin creates a new "Wiki" section within JIRA, that can be seen from the main JIRA header. This is where all your SimpleWiki pages live.

It also adds a new shortcut that allows you to easily mention wiki pages from JIRA issues. Just type # and begin typing the name of a page, and similar to mentioning users, you will see a list of pages to link to.

Additionally, SimpleWiki provides several new Dashboard widgets that allow you to put a list of pages on a JIRA dashboard, or show the contents of a single page. Ideal for a custom welcome page with lots of details and links.

Unfortuntately, that's the way Atlassian handles all licensing.

Regardless of how many users need an app, you end up having to pay for all users in your Jira Cloud instance. This behavior is enforced on the Atlassian side, and outside of our control.

If you can think of a feature you would like to see in SimpleWiki, don't hesitate to email us at support@tss.io, and let us know about it.

We are always looking for ways to improve our plugins, and the best way to do that is with your input.

SimpleWiki does not use any special markup language besides what ships natively with JIRA itself. Authoring wiki pages within SimpleWiki is exactly like writing descriptions and comments for JIRA Issues. You simply use the same tags as you normally would.

For a guide on authoring pages, and some of the formatting options, take a look at our Documentation.

Yes they do.

You can attach any file they like to a page, and reference the file within the page, which will be displayed as a link.

You can also embed images into a page directly.

Not yet. This is a feature that will be coming in a future release.

You can however embed individual images into a page directly.

Not yet. This is a feature that will be coming in a future release.

Pages keep track of their full history. You can simply go to the page history screen, and find past versions of the page, and look at them. You can then either copy/paste the content you accidentally removed, or revert the entire page to a previous version.

Nope. Once a page is deleted, it is gone forever.

Pages support a wide array of permissions settings, allowing you to protect a page, so only users from specific groups, or with specific roles, or even individual users have access to a page.

This allows you to control who can view, and who can edit a page.

On Jira Server / Data Center, you can mark a page as 'public', in which case the page receives a separate public url that is accessible by users outside of Jira. Public users will be able to see the page content, as well as any files/images embedded into the page, but they won't be able to edit the page, delete it, or access any other page data like history, versions, or other attachments not mentioned within the page body.

On Jira Cloud, pages cannot be shared with anyone outside of Jira.

Team pages does not have this capability yet, but it is something we are exploring for future versions.

You can install the plugin directly from your Jira instance by visiting the "Find new Apps" page, and searching for 'Simple Team Pages'.

Once installed, you're immediately ready to go. There are no special configuration steps or settings you need to adjust.

Atlassian provides customers with a Sandbox Jira Cloud instance. You can install the app there for testing purposes.

Additionally, you could sign up for a new Jira Cloud evaluation, and install it there as well to test out things.

For Server / Data Center instances, Atlassian provides developer licenses for testing purposes, and also allows evaluation licenses that run much longer than Jira Cloud. If you need help with this, simply contact our support.

After install, you will see a new "Wiki" menu item in the main Jira navigation. Additionally, you will also see a "Wiki Pages" item in the project sidebar for each project.

Jira Cloud apps are typically upgraded automatically by Atlassian whenever we make a release in the marketplace.

The exception to that is if we require additional permissions from you. In that case, you have to manually upgrade from the "Manage Apps" screen, by clicking the upgrade button, as this grants us the additional permissions we request.

Jira Server / Data Center does not automaticalyl upgrade apps.

You will have to visit the Manage Apps screen to perform any updates.

If an update is available, the Manage Apps screen will indicate that.

Before upgrading any app, we highly suggest creating a backup of your data.

You can either uninstall the app from the "Manage Apps" screen, and then reinstall from the Atlassian Marketplace.

Uninstalling the app keeps your Tasks and Templates in tact. Thus, if you reinstall the app after uninstalling it, your data will come right back.

On Jira CLoud, when you uninstall we hold on to your data until your subscription expires.

Once your subscription (or evaluation) is marked as expired or cancelled, we delete your data within 7 days

On Jira Server / Data Center, the data remains in your Jira Database until it is manually removed. If you were to reinstall the app months, or years later. In theory, your old tasks would come back.

Pages are stored in our infrastructure, outside of Jira Cloud.

We encrypt all data at rest, and backup our data daily.

The plugin maintains a separate set of tables in the Jira Database. All the wiki content is stored there, and thus automatically part of your backup strategy if you backup the Jira database. (you do have a backup strategy, right??).

File attachments for Wiki pages are stored in a separate wiki folder within the Jira home folder on your Jira server.

On Jira Cloud, we store files in S3.

In theory, you shouldn't have to do anything special to backup the Wiki data. Your normal Jira backups should be sufficient.

To be more precise however, you'll need to backup the database tables, and ensure that your Jira home folder is backed up. We store attachments there in a separate "wiki" folder.

Currently there is no way for you to backup your data separately. We run backups daily however.