2 0 2 4 /2025 | © copyright | This work may not be copied for profit gain Excel!
Project Administration in Jira Server ACP-
600 Questions and Answers 2024/2025
Wiki Style Renderer
displays rich text (HTML)
Workflow Scheme
determines which workflows (issue state transitions) apply to issue types in this project.
Screen Scheme
determines which screens are displayed for each issue operations (view, edit, create);
Associate one screen scheme with each issue type in the "Issue Type Screen Scheme"
Issue Type Screen Scheme
determines which screens are displayed for different issue operations (view, edit,
create), for different issue types.
field configuration
setting each field to be required/optional, rich text/plain text, hidden/visible
Field Configuration Scheme
determines which field configuration applies to issue types in this project. (A field
configuration determines each field's overall visibility, requirements, formatting
(wiki/rich-text or plain) and help-text).
Settings
Application Links (Confluence, Fisheye, Jira)
1|Page| GradeA+ | 2 0 0 2 5
,2 0 2 4 /2025 | © copyright | This work may not be copied for profit gain Excel!
Project Lead
user fulfilling the role of project leader. Used as the 'Default Assignee' (except for
Jira Software projects where it is set to 'Unassigned'), and potentially elsewhere in Jira
(e.g. in permission schemes, notification schemes, issue security schemes and workflows).
Default Assignee
the user to whom issues in this project are initially assigned when created. Can be
either the 'Project Lead' (above), or, if Allow unassigned issues is set to 'On' in Jira's
general configuration, 'Unassigned'. There are also default component assignees.
Default Assignee on new projects?
By default, new projects also have their 'Default Assignee' set to 'Unassigned.'
Project Roles
members are users/groups who fulfill particular functions for this project.
Versions
Versions can also have a Release Date, and will automatically be highlighted as
"overdue" if the version is unreleased when this date passes.
Components
Issues can belong to multiple components. You can choose a default assignee for each
component, which is useful if you have different people leading different sub-teams in
your project.
Permission Scheme
the project's permission scheme determines who has permission to view or change
issues in this project.
1|Page| GradeA+ | 2 0 0 2 5
,2 0 2 4 /2025 | © copyright | This work may not be copied for profit gain Excel!
Issue Security Scheme
the project's issue security scheme determines what visibility levels issues in this project
can have
Notification Scheme
determines who receives email notifications of changes to issues in this project.
Email
specifies the 'From' address for emails sent from this project.
Default Notification Scheme
associated with all new projects by default. Starts emailing at first triggered event.
Development tools availability
only available on Jira Software projects, and can only be viewed by Jira Software
users.
Development Tools
overview of the development tools that are connected and which users can use the
integration features between them
Development Tools: View permission
lists which users can see the development tools integration features (like the Create
Branch link) on the view issue screen, as well as other development-related information,
like commits, reviews and build information. This ability is controlled by the "View
Development Tools" project permission.
Development Tools: Applications
1|Page| GradeA+ | 2 0 0 2 5
, 2 0 2 4 /2025 | © copyright | This work may not be copied for profit gain Excel!
This section shows which development tools are connected to Jira via application links
and are eligible to use the development tool features in Jira.
Administer Projects Permission
Edit the project name, description, avatar image, URL, lead, and role membership, &
project type. Define components & versions. View, but not edit project schemes.
Global permission
These apply to applications as a whole, not individual projects. People who may have
them: A user with the Jira System administrator permission
A user in a group with Admin access
Project permission
who can see the project's issues, create, edit and assign them
Issue security permission
Organized into security schemes, these allow the visibility of individual issues to be
adjusted (within the bounds of the project's permissions). For example, issue security
permissions can let you set up types of issues that can only be seen by project admins
or users in specific groups. Project Admin's can set these.
Board administration permissions
changing the configuration of a board. For example, changing columns, customizing
cards, etc.
Board usage permissions
creating sprints, ranking issues, etc. Board usage permissions are derived from project
permissions.
1|Page| GradeA+ | 2 0 0 2 5
Project Administration in Jira Server ACP-
600 Questions and Answers 2024/2025
Wiki Style Renderer
displays rich text (HTML)
Workflow Scheme
determines which workflows (issue state transitions) apply to issue types in this project.
Screen Scheme
determines which screens are displayed for each issue operations (view, edit, create);
Associate one screen scheme with each issue type in the "Issue Type Screen Scheme"
Issue Type Screen Scheme
determines which screens are displayed for different issue operations (view, edit,
create), for different issue types.
field configuration
setting each field to be required/optional, rich text/plain text, hidden/visible
Field Configuration Scheme
determines which field configuration applies to issue types in this project. (A field
configuration determines each field's overall visibility, requirements, formatting
(wiki/rich-text or plain) and help-text).
Settings
Application Links (Confluence, Fisheye, Jira)
1|Page| GradeA+ | 2 0 0 2 5
,2 0 2 4 /2025 | © copyright | This work may not be copied for profit gain Excel!
Project Lead
user fulfilling the role of project leader. Used as the 'Default Assignee' (except for
Jira Software projects where it is set to 'Unassigned'), and potentially elsewhere in Jira
(e.g. in permission schemes, notification schemes, issue security schemes and workflows).
Default Assignee
the user to whom issues in this project are initially assigned when created. Can be
either the 'Project Lead' (above), or, if Allow unassigned issues is set to 'On' in Jira's
general configuration, 'Unassigned'. There are also default component assignees.
Default Assignee on new projects?
By default, new projects also have their 'Default Assignee' set to 'Unassigned.'
Project Roles
members are users/groups who fulfill particular functions for this project.
Versions
Versions can also have a Release Date, and will automatically be highlighted as
"overdue" if the version is unreleased when this date passes.
Components
Issues can belong to multiple components. You can choose a default assignee for each
component, which is useful if you have different people leading different sub-teams in
your project.
Permission Scheme
the project's permission scheme determines who has permission to view or change
issues in this project.
1|Page| GradeA+ | 2 0 0 2 5
,2 0 2 4 /2025 | © copyright | This work may not be copied for profit gain Excel!
Issue Security Scheme
the project's issue security scheme determines what visibility levels issues in this project
can have
Notification Scheme
determines who receives email notifications of changes to issues in this project.
specifies the 'From' address for emails sent from this project.
Default Notification Scheme
associated with all new projects by default. Starts emailing at first triggered event.
Development tools availability
only available on Jira Software projects, and can only be viewed by Jira Software
users.
Development Tools
overview of the development tools that are connected and which users can use the
integration features between them
Development Tools: View permission
lists which users can see the development tools integration features (like the Create
Branch link) on the view issue screen, as well as other development-related information,
like commits, reviews and build information. This ability is controlled by the "View
Development Tools" project permission.
Development Tools: Applications
1|Page| GradeA+ | 2 0 0 2 5
, 2 0 2 4 /2025 | © copyright | This work may not be copied for profit gain Excel!
This section shows which development tools are connected to Jira via application links
and are eligible to use the development tool features in Jira.
Administer Projects Permission
Edit the project name, description, avatar image, URL, lead, and role membership, &
project type. Define components & versions. View, but not edit project schemes.
Global permission
These apply to applications as a whole, not individual projects. People who may have
them: A user with the Jira System administrator permission
A user in a group with Admin access
Project permission
who can see the project's issues, create, edit and assign them
Issue security permission
Organized into security schemes, these allow the visibility of individual issues to be
adjusted (within the bounds of the project's permissions). For example, issue security
permissions can let you set up types of issues that can only be seen by project admins
or users in specific groups. Project Admin's can set these.
Board administration permissions
changing the configuration of a board. For example, changing columns, customizing
cards, etc.
Board usage permissions
creating sprints, ranking issues, etc. Board usage permissions are derived from project
permissions.
1|Page| GradeA+ | 2 0 0 2 5
