Atlassian Managing Jira Projects for Data Center Exam Syllabus

• What is unique in each project (name, key, description, avatar, versions, components, role membership, etc.)?
• Which global settings are required in order to use boards, release hub, etc?
• Which schemes are unique and which are shared when projects are created from a template?
• What are the differences in functionality provided by each project template?
• What are the impacts of creating projects with shared configuration?
• What are all the project schemes and who can update them?
• What are the impacts of updating a shared scheme

- Given business requirements, recommend an issue type configuration for a project
- This topic includes:

• When is a new issue type required?
• What is the impact of changing the order of issue-types for a project?
• What are the implications of setting the default issue type?
• Who can configure issue types?
• What is the relationships between epics, stories, andsub-tasks?

- Describe how to manage general project configurations (project details, project sidebar)
- This topic includes:

• Who can update general project permissions?
• What can be updated in the project sidebar?
• Which project details can be updated?
• What is the impact of changing the project lead and default assignee?
• What is the impact of changing the project name and key?

• How is the Kanban backlog configured and what are the benefits and impacts?
• How are epics managed on a board?
• Which panels are available for each board type?
• What board configurations are available in each board type?
• Which reports are available in each board type?

- Given business requirements, configure boards across multiple teams and projects
- This topic includes:

• How are board filters configured to show multiple projects on a single board?
• What business requirements warrant doing this?
• What are the implications?
• How can you use quick filters and swimlanes to manage boards?
• When would you use parallel sprints?
• What permissions are needed to update board filters?

- Configure board columns to match a workflow process
- This topic includes:

• When would you add new statuses?
• What are the implications of status to column mapping?
• What happens if more than one status is mapped to a single column?
• Which permissions are needed to add board columns?
• Which permissions are needed to add a status when adding a column?

- Translate requirements into board filters, sub-filters, and quick filters
- This topic includes:

• Why would you update the board filter?
• What are the impacts of doing so (e.g. issues will or will not be included in reports)?
• Which boards use sub-filters and what are sub-filters used for?
• How and why are quick filters configured?

- Determine the effects of estimation and time tracking on Scrum boards
- This topic includes:

• What are the differences across boards for managing estimation and time tracking?
• Where in Jira is time tracking is managed?
• Why might users be unable to log time?
• What estimation statistics are available and what are their benefits and implications?
• What happens when an estimation statistic is changed?
• What are the impacts of scope changes?

- Configure board swimlanes, card colors, card layout, working days, and issue detail view
- This topic includes:

• Why is one board configuration more suitable than another?
• What are all the available board configurations?
• What are the configuration differences between board types?
• What are the impacts and limitations of using swimlanes by query?

- Troubleshoot board and filter configurations
- This topic includes:

• How can you share the viewing and editing of a filter?
• Who can transfer the ownership of a filter, and where?
• Why might you see more or fewer issues in a search result versus on a board?

• What are all the project permissions, and what do they allow?
• Which permissions are used used in combination?
• What are all the global permissions?
• Why do you use issue-level security, how is it configured, what permissions are involved, and what are its implications?

- Assign team members to project roles
- This topic includes:

• Who can assign members to project roles?
• Who can create a project role?
• Who can associate a project role with a project permission?

- Implement versioning, manage releases, predict the impact of scope changes
- This topic includes:

• What happens to unresolved issues when a version is being released?
• What information is available in the release hub?
• Who can manage versions?
• What information can be added to a version (start date, end date, name, description)?
• How is an issue associated with a version in the issue itself and on a board?

- Recommend a method to sub-categorize issues (components, labels, custom fields)
- This topic includes:

• What functionality is available with labels, components, custom fields?
• When would you use one versus another?
• Who can create labels, components and custom fields?
• How are components managed?

- Configure and troubleshoot automatic issue assignment (project default, components)
- This topic includes:

• How do components and automatic issue assignment work?
• What is the implication of selecting more than one component?

- Demonstrate knowledge of bulk operations
- This topic includes:

• What are the limitations of bulk operations?
• Which global and project permissions are required to perform a bulk operation?

- Evaluate ways to enrich issues (attachments, links, time tracking, developer information
- This topic includes:

• How do you link issues?
• Which project and global permissions are needed to attach, to link, to add time-tracking and developer information to an issue?

- Demonstrate knowledge of issue archiving
- This topic includes:

• What are the implications and benefits of archiving issues?
• Who can archive and restore issues?

• What are the prerequisites for project administrators to manage fields on project screens?
• What can they do and what are the limitations?

- Given a scenario, determine the appropriate method to edit project workflows to meet business needs
- This topic includes:

• What are the prerequisites for project administrators to edit workflows?
• What can they do and what are the limitations?
• What are the differences between advanced and simplified workflows?
• What are the implications of editing a simplified workflow?

• What is valid JQL syntax (fields, functions, operators, keywords)?

- Determine an appropriate report, gadget, and dashboard configuration
- This topic includes:

• What are all the agile reports and issue analysis reports?
• Which gadgets provide which types of information?
• How do you configure gadgets?
• What is the impact of updating and modifying a filter that is associated with a gadget?
• What is the impact of sharing/not sharing a filter or dashboard?
• How can you edit and share dashboards?
• Which report should you use, when?

- Analyze information from agile reports and issue analysis reports
- This topic includes:

• What information can you get from all the agile and issue analysis reports available to every project type?