Exam (elaborations)
PROJECT ADMINISTRATION IN JIRA SERVER ACP-600 EXAM.
- Course
- Institution
PROJECT ADMINISTRATION IN JIRA SERVER ACP-600 EXAM...
[Show more]
Content preview
Wiki Style Renderer - ANSWER displays rich text (HTML)Workflow Scheme - ANSWER determines which workflows (issue state
transitions) apply to issue types in this project.
Screen Scheme - ANSWER determines which screens are displayed for
each issue operation (view, edit, create); Associate one screen scheme
with each issue type in the "Issue Type Screen Scheme"
Issue Type Screen Scheme - ANSWER determines which screens are
displayed for different issue operations (view, edit, create), for different
issue types.
field configuration - ANSWER setting each field to be required/optional,
rich text/plain text, hidden/visible
Field Configuration Scheme - ANSWER 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 - ANSWER Application Links (Confluence, Fisheye, Jira)
Project Lead - ANSWER 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 - ANSWER 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? - ANSWER By default, new projects
also have their 'Default Assignee' set to 'Unassigned.'
Project Roles - ANSWER members are users/groups who fulfill particular
functions for this project.
Versions - ANSWER Versions can also have a Release Date, and will
automatically be highlighted as "overdue" if the version is unreleased
when this date passes.
Components - ANSWER 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 - ANSWER the project's permission scheme
determines who has permission to view or change issues in this project.
Issue Security Scheme - ANSWER the project's issue security scheme
determines what visibility levels issues in this project can have
Notification Scheme - ANSWER determines who receives email
notifications of changes to issues in this project.
Email - ANSWER specifies the 'From' address for emails sent from this
project.
Default Notification Scheme - ANSWER associated with all new projects
by default. Starts emailing at first triggered event.
Development tools availability - ANSWER only available on Jira
Software projects, and can only be viewed by Jira Software users.
Development Tools - ANSWER overview of the development tools that
are connected and which users can use the integration features between
them
, Development Tools: View permission - ANSWER 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 - ANSWER 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 - ANSWER 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 - ANSWER 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 - ANSWER who can see the project's issues, create,
edit and assign them
Issue security permission - ANSWER 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 - ANSWER changing the configuration
of a board. For example, changing columns, customizing cards, etc.
Board usage permissions - ANSWER creating sprints, ranking issues,
etc. Board usage permissions are derived from project permissions.
Manage sprints' permission - ANSWER to perform sprint-related actions,
users need the 'Manage sprints' permission for all projects in the origin
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying these notes from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller luzlinkuz. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for $11.49. You're not tied to anything after your purchase.
Can Stuvia be trusted?
4.6 stars on Google & Trustpilot (+1000 reviews)
79650 documents were sold in the last 30 days
Founded in 2010, the go-to place to buy study notes for 14 years now