Configuring screens and schemes

Question 1

Cite 3 or 4 interactions with an issue where screens can be added

Answer 1

Create
View & Edit
Transition (via workflow)

Question 2

Difference in administrating Create vs View/Edit screen ?

Answer 2

Fields are managed on the Create screen directly
vs
fields are managed via Issue layout for view/edit screens

Question 3

Screen layout vs issue layout

Answer 3

Screen layout = Global : Jira Admin

Issue layout = by project : Project Admin

Question 4

Issue layout : what can a Project Admin do ?

Answer 4

Change field
Order
Conditional visibility
Visibility (completely hide)

Question 5

Issue layout : what a Project Admin can’t do ?

Answer 5

Add fields

Remove fields

Question 6

2 default screens for Software projects

Answer 6

Bug screen

Default issue screen

Question 7

2 default screens for business projects

Answer 7

Create Issue

View / Edit issue

Question 8

2 ways to remove a system field from a screen

Answer 8

Remove from the screen itself
(won’t affect search & reporting)
Hide in Field configuration
(field is no more searchable or usable)

Question 9

What happens to a hidden field with a default value when an issue is created ?

Answer 9

The default value is not populated

Question 10

2 ways to remove a custom field from a screen

Answer 10

Remove from screen
(existing data preserved)
Delete custom field
(!! existing data destroyed)

Question 11

what is a screen scheme

Answer 11

A mapping between screens and issue operations

Question 12

What are the 2 default screen schemes for a software project ?

Answer 12

Bug Screen scheme:
Create, Edit and View for Bug issue type use Bug Screen
Default Screen scheme:
Create, Edit and View for all other issue type use Default issue screen

Question 13

What is the default screen scheme for a business project ?

Answer 13

“Project” Screen scheme :
Create operation uses Create Issue screen
Edit / View operations use Edit/View Issue screen

Question 14

You can only delete a screen if .. (2 conditions)

Answer 14

Not used in any screen scheme

Not used in any WF

Question 15

You can only delete a screen scheme if ..(1 condition)

Answer 15

Not used in an issue type screen scheme

Question 16

What is an Issue type screen scheme

Answer 16

A mapping between issue types and screen schemes

Question 17

what are the 2 default issue type screen schemes for a SW project ?

Answer 17

Bug
(=Bug issue type to Bug screen scheme)
Unmapped Issue Types
(= Any other issue type to Default screen scheme)

Question 18

what is the default issue types screen scheme for a business projects ?

Answer 18

All Issue types

= any issue type to “project” Screen scheme

Question 19

What conditions (5) must be met for a user to see a field ?

Answer 19

Field must be present on the current operation screen
Field not hidden via issue layout
Field not hidden in field configuration applicable to the current issue
User has permission to edit the fields
Some fields require specific perms (e.g. Due Date requires Schedule Issues perm)