Questions and Answers| 100% Solved
What requirements must a user meet in order to use a particular workflow transition?
✔️✔️Transition issues permission, any transition conditions. (Browse project)
What is an Issue Collector and what permissions are needed to configure it? ✔️✔️It allows you to
embed a feedback form into your website so users can create issues. Can only be set up by Jira
Administrator (global permission).
Where are all the places you need to look to fully identify what permissions a particular user
has? ✔️✔️Check all projects user can access, indiv. user project permissions , roles on project;
also groups user belongs to and global permissions.
What are the use cases where it is best to use Project Roles rather than Groups? ✔️✔️
Which business requirements necessitate the use of separate issue types in a project?
✔️✔️Anything requiring different Create, View, Edit screens, including fields not in the
configuration; different workflows or transitions; disaggregation in reports
What is the relationship between screens, screen schemes and issue type screen schemes? •
How are they related to field configurations? ✔️✔️Screens contain fields, which are defined and
set as visible in the field configuration. Screen schemes contain screens for Create, View & Edit.
Issue type Screen Schemes list which screen scheme is used for each issue type.
How do you determine the maximum number of screens possibly used in a project? ✔️✔️3
(Create, View, & Edit) * # of Issue Types, + # of Workflow transitions
Who can make changes to screens, screen schemes and issue type screen schemes? ✔️✔️Only
Jira Administrators
,What are all the various factors that influence whether a field is visible on a screen? ✔️✔️Hidden
in field configuration; Security Level; User permissions; field context not for this project; no
value for project; user has hidden it in configure field settings
When is it best to use components, and when is it best to use a custom field instead?
✔️✔️Components: When you need default assignee and multiple choices. Custom Field: When
you need something across projects, you need a default value, you need a single-choice
dropdown.
What are the features, uses, limitations/restrictions of workflow changes, especially the
Simplified Workflow? ✔️✔️
Who can change the Simplified Workflow? What are the limitations on changes to the
Simplified Workflow? ✔️✔️
What changes can be performed on statuses and transitions? ✔️✔️
What things may need to be updated as a result of workflow changes of any kind? ✔️✔️
What workflow changes can be done through the board by board administrators? ✔️✔️
What types of workflow changes can Project Administrators make if Extended Project
Administration is enabled? ✔️✔️
How do these settings affect notifications? • AutoWatch setting • My Changes setting • Share
This Issue • @Mentions • Filter Subscriptions ✔️✔️AutoWatch sends notifications to users when
issues meeting JQL query rules are created or changed. Users can disable AutoWatch and won't
be notified. Users can also set whether they want notifications about changes they made.
@Mentions send a notification (they can uncheck the box in their settings), Subscribing to a
Filter gets notifications
, How are valid JQL queries written? What operators and arguments are valid for various JQL
functions (e.g. membersOf(), StartOfDay(), WAS, CHANGED, etc.) ✔️✔️
Which export options are available from the Issue Navigator? ✔️✔️HTML, CSV, XML, Word
Given a scenario, select changes to issue links, time tracking, priorities and resolutions ✔️✔️
Can project managers edit the workflow? ✔️✔️Yes, by replacing global transitions and settining
initial status. Only JA's can set conditions or trigger events.
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).