Classic Settings • Documentation
The app for Jira and Service Desk Cloud next-gen projects admins
- 1 Welcome
- 2 Installation
- 2.1 Platforms
- 2.2 Prerequisites
- 3 Technical details
- 3.1 Privacy
- 4 Integrations
- 5 Available settings
- 5.1 Details
- 5.1.1 Project lead
- 5.1.2 Default assignee
- 5.1.3 URL NEW
- 5.1.4 Description BETA
- 5.1 Details
Welcome
We designed Classic Settings with your comfort and with your team and company needs in mind.
From garage startups to global enterprises, from contractor to owner, Classic Settings aims to give you exactly what you need, with a smooth experience.
More updates with new features are coming soon…
Installation
Available on the Atlassian Marketplace and inside the Universal Plugin Manager inside your Jira Cloud instance.
Platforms
Classic Settings is an installable Jira app, available for the following platforms:
Prerequisites
An active Jira Cloud instance you have the permission to install apps on.
No need to look for those permissions. Jira will let you know in a few steps. If you cannot install apps, please refer to your Jira administrator for permissions, or with the Classic Settings Atlassian Marketplace listing.A next-gen project you are a project administrator for.
No need to look for those permissions. Jira will let you know in a few steps. If you have sufficient permissions, you’ll see the project settings menu item and you will be able to access the project settings.
Otherwise, please contact your project administrator to elevate your project permissions or use the settings offered by the plugin for you.
Technical details
Classic Settings brings you a simple user friendly experience by translating some of the flexibility classic projects offer into next-gen projects. As in all of our products, we aspire to integrate seamlessly into the platform we help you enjoy. For our Atlassian apps we achieve that by consulting every decision with Atlassian Design guidelines, and using Atlassian’s own new AtlasKit as our client side framework.
As part of our efforts to keep you safe and comfortable, we save only the data that we need, and only on your own Jira instance alongside the rest of your Jira data. For those reasons, our servers don’t take part in any data handling or logic. This means your connections and data are always secure at the same high standards. This policy is of course endorsed by Atlassian, and you’ll be happy to know we use all the tools and best practices provided to achieve it.
Privacy
Classic Settings is served over a secure connection, and is completely client side and anonymous.
Nevertheless, we understand your company or industry might require extra care. To avoid any risk, and the privacy policy hunt, we add a short readable disclosure of our data handling.
Data disclosure:
On our servers: No data saved by the app.
On third party servers: No data saved by the app.
On your Jira instance:
The settings you configure per project. - You can always view it in your project settings' apps section.
Integrations
Integration is as expected from this app category.
A new next-gen project settings app.
A menu item called “Classic Settings“ will be added.
The app itself opens as a standard system page from said menu item.
App page contains the desired form.
Available settings
No all settings will be added for a couple of reasons. Not everything possible to support safely, some settings just don’t fit the spirit of next-gen projects, and others are just not missed. That said, we are considering bringing the entire old form experience back for us keyboard lovers. Anyway, a lot more to come very soon…
Details
The section is named after the beloved section found classic project settings.
Project lead
Configure and change the project lead.
Type: User picker.
Default: Current saved value – defaults to project creator.
Required: Yes.
Validation: A valid user permitted to be the project lead.
Permissions are handled automatically by the closest standard Jira mechanism we found.
We utilize it to enforce that the selected can indeed by an assignee for this project’s issues.
This should allow Project Admins as well as Project Members to be set as project lead
Disabled: Never.
Default assignee
Choose the default assignee behaviour.
Type: List.
Options:
“Project lead”.
"Unassigned".
Default: Current saved value – defaults to “Project lead“.
Required: Yes.
Validation: Any one of the available values.
Disabled: Never.
No option is ever disabled either.
URL NEW
Setup a project URL.
This field determines the link that will be available in project summaries and project tables used for search or administration.
Type: Text.
Default: Empty.
Required: No.
Validation: A valid URL address starting with
http://
orhttps://
.Any character is accepted.
Trims leading and trailing whitespace.
Disabled: Never.
Description BETA
Describe your project using the standard Atlassian rich text editor.
Type: Rich text.
Default:
Required: No.
Validation: None.
Disabled: Never.
Are you missing text editor features?
This feature is release as BETA and does not yet support all the amazing features the Atlassian rich text editor provides. Some features don’t fit without an issue context, and others will be slowly released making sure everything works sa expected for you and your organization. Please contact our service desk if you think we missed something, or just let us know what features you covet the most.