No, you can't buy the Server version of the app, but we have a solution for your use case. Despite the new server app sales ended, you can buy or generate a trial Data Center license for Smart Attachments and install it on your Jira Server instance as they are compatible.
Yes, the app supports document revisions. You can upload files with the same name and the app will automatically match it to the parent document. You can also select a document revision manually from files already stored in the issue.
Yes, you can limit access to specific categories. You can restrict access to categories for specific users, user groups, and project roles. The app can also restrict access to categories on the basis of values from the single and multi user / user group pickers. In this case, the visibility of your categories will be dynamically based on values of these fields.
Yes, the app matches files by name and keeps them as a tree of revisions.
Yes, the app provides bulk operations for deleting, moving between categories, sending by email, archiving and downloading attachments.
Yes, the app provides the project storage. You can manage its structure and upload folders with files with the automatic folder structure recreation. Your teammates can instantly locate project documents in one place.
You may not be able to delete attachments in the following situations:
You are not able to delete the document that contains revisions loaded by other users if you do not have a permission to delete all attachments in the project.
They will remain in JIRA issues as standard attachments.
They will be stored in JIRA issues as uncategorized.
The add-on provides a convenient way of showing attachments grouped by categories in JIRA.
For example, categories will be useful:
The add-on allows you find its applicability to any sphere of your activity.
Our app doesn't affect the preview of attachments. It depends on the Atlassian Jira limitation. You can vote for this request in the Atlassian backlog.
This is a known issue for Smart Attachments add-on when using it along with Oracle database.
As a temporary workaround, please do the following:
Please ensure that you are using Smart Attachments 1.16.7 or newer versions before disabling this component. |
Our migration documentation mentions only the JCMA migration method. If you're considering the site import method, the app data will not be migrated with this method. You don't need to have all the projects migrated with JCMA to migrate the data about the apps categories (their IDs and names). The migration of one project will be enough to transfer the category data.
For Jira 9.X you'll need Smart Attachments 2.14.X.
If you have an issue with it, please, check for the app configuration in the Manage apps section. By default, our app has 82 out of 83 modules enabled.
The *attach-cat-webwork-jira-8* module should be disabled. When enabled manually, it can cause an issue in your Jira environment.
we don't have this functionality but we can suggest a workaround. You can disable the storage in all the projects and then use a CSS to block the ability for project admins to enable the toggle for the project storage activation.
Use this CSS to disable the toggle for all projects:#app-container[data-section="storage"] label {
2 pointer-events: none;
3}
Use this CSS to disable the toggle for a specific project (projectkey - TP here):#app-container[data-section="storage"][data-project-key="TP"] label {
2 pointer-events: none;
3}
Jira doesn’t provide any information about cloning issues, and our app can not track when exactly attachments are created after cloning an issue.
A workaround is to restrict cloning issues.
Our app listens to the general Jira workflow events. If you have a custom event fired on the post function, the app's behavior may be unexpected. You need to estimate the possible impact of such changes.