How can I revert back my default scheme? I have changed it and now I do not remember the settings

plekeas1 June 4, 2016

This question is in reference to Atlassian Documentation: Managing project permissions

How can I revert back my default scheme? I have changed it and now I do not remember the settings

2 answers

1 accepted

1 vote
Answer accepted
Meck
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 4, 2016

Hello Paraskevas,

Did you overwrite the permission scheme? 

I do not know if this is possible, but lemme know what's your project type and I'll send to you what is the default scheme.

A Workaround is:

Create a project to see what is the default.

 

The default to JIRA CORE is:

Project Permissions

PermissionUsers / Groups / Project Roles
Administer Projects
Ability to administer a project in JIRA.
  • Project Role (Administrators)
Browse Projects
Ability to browse projects and the issues within them.
  • Application access (Any logged in user)
Manage Sprints
Ability to manage sprints.
  • Project Role (Administrators)
Service Desk Agent
Allows users to interact with customers and access Service Desk features of a project.
 
View Development Tools
Allows users in a software project to view development-related information on the issue, such as commits, reviews and build information.
  • Application access (Any logged in user)
View Read-Only Workflow
Users with this permission may view a read-only version of a workflow.
  • Application access (Any logged in user)

Issue Permissions

PermissionUsers / Groups / Project Roles
Assignable User
Users with this permission may be assigned to issues.
  • Application access (Any logged in user)
Assign Issues
Ability to assign issues to other people.
  • Application access (Any logged in user)
Close Issues
Ability to close issues. Often useful where your developers resolve issues, and a QA department closes them.
  • Application access (Any logged in user)
Create Issues
Ability to create issues.
  • Application access (Any logged in user)
Delete Issues
Ability to delete issues.
  • Project Role (Administrators)
Edit Issues
Ability to edit issues.
  • Application access (Any logged in user)
Link Issues
Ability to link issues together and create linked issues. Only useful if issue linking is turned on.
  • Application access (Any logged in user)
Modify Reporter
Ability to modify the reporter when creating or editing an issue.
  • Project Role (Administrators)
Move Issues
Ability to move issues between projects or between workflows of the same project (if applicable). Note the user can only move issues to a project he or she has the create permission for.
  • Application access (Any logged in user)
Resolve Issues
Ability to resolve and reopen issues. This includes the ability to set a fix version.
  • Application access (Any logged in user)
Schedule Issues
Ability to view or edit an issue's due date.
  • Application access (Any logged in user)
Set Issue Security
Ability to set the level of security on an issue so that only people in that security level can see the issue.
 
Transition Issues
Ability to transition issues.
  • Application access (Any logged in user)

Voters & Watchers Permissions

PermissionUsers / Groups / Project Roles
Manage Watchers
Ability to manage the watchers of an issue.
  • Project Role (Administrators)
View Voters and Watchers
Ability to view the voters and watchers of an issue.
  • Application access (Any logged in user)

Comments Permissions

PermissionUsers / Groups / Project Roles
Add Comments
Ability to comment on issues.
  • Application access (Any logged in user)
Delete All Comments
Ability to delete all comments made on issues.
  • Project Role (Administrators)
Delete Own Comments
Ability to delete own comments made on issues.
  • Application access (Any logged in user)
Edit All Comments
Ability to edit all comments made on issues.
  • Project Role (Administrators)
Edit Own Comments
Ability to edit own comments made on issues.
  • Application access (Any logged in user)

Attachments Permissions

PermissionUsers / Groups / Project Roles
Create Attachments
Users with this permission may create attachments.
  • Application access (Any logged in user)
Delete All Attachments
Users with this permission may delete all attachments.
  • Project Role (Administrators)
Delete Own Attachments
Users with this permission may delete own attachments.
  • Application access (Any logged in user)

Time Tracking Permissions

PermissionUsers / Groups / Project Roles
Delete All Worklogs
Ability to delete all worklogs made on issues.
  • Project Role (Administrators)
Delete Own Worklogs
Ability to delete own worklogs made on issues.
  • Application access (Any logged in user)
Edit All Worklogs
Ability to edit all worklogs made on issues.
  • Project Role (Administrators)
Edit Own Worklogs
Ability to edit own worklogs made on issues.
  • Application access (Any logged in user)
Work On Issues
Ability to log work done against an issue. Only useful if Time Tracking is turned on.
  • Application access (Any logged in user)
1 vote
Joe Pitt
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 5, 2016

You can't.  The best you can do is download the evaluation version under a different name, maybe a personal email, install it and then review the defaults. This is one of the 'lessons learned'; never modify the default, create a new one and use it. This goes for pretty much all the schemes in my book.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events