ACP-620 Managing Jira Projects for CloudExam Questions and Answers

A Sub-task is always tied to its parent issue and cannot exist independently in a sprint. It is automatically included in the same sprint as its parent, ensuring the work is tracked together.

The Card layout controls which fields are displayed on issue cards in the backlog and board views. To show the Color custom field on both boards, it must be added to the card layout configuration for each board individually.

The Schedule Issues permission is required to edit date-related fields, such as the Due Date and Fix Versions. Since the rule edits the Fix versions field and responds to Due Date changes, lacking this permission will cause the rule to fail.

In a company-managed Kanban project, the board can have multiple In Progress statuses from different workflows mapped to the same column. This allows teams to visually group similar types of work even if the statuses come from different issue types or workflows. It provides flexibility without requiring one column per status.

Changing the Standard Working Days affects the Burndown Chart, as this chart relies on working days to plot the ideal and actual burn of work during a sprint. Adjusting working days ensures the burndown chart accurately reflects the team's actual schedule.

To allow Ravi to maintain quick filters and grant that ability to others, you need to make him a board administrator. Board administrators can manage board settings, including quick filters, and can also assign board admin rights to others.

The Pie Chart gadget can be configured based on a Project (not only a saved filter) and provides a graphical representation of issue distribution, such as by Status, Priority, or Assignee - meeting both specified criteria.

priority changed to High before now(): This returns issues where the priority was set to High at any point in the past, regardless of its current value.

priority was High: This returns issues that had High priority at some point, whether or not they still have it. Both satisfy the requirement to show issues where the priority was High in the past and may or may not still be.

Some of the issues are hidden by issue security levels: Amanda may not have permission to view issues restricted by security levels, causing her to see fewer results.

She does not meet the currentUser() criteria in the saved filter: If the saved filter uses currentUser() in its JQL and Amanda doesn’t match its logic, the results shown to her will differ from those seen by others.

An automation rule is the best way to automatically assign unresolved issues to Ken at the end of each day. It can be scheduled to run daily, check for unresolved issues, and assign them to a specific user without manual intervention.

Modifying the board sub-filter allows you to exclude Done issues from the board view after they are moved to that status, while still keeping them in Jira and visible in reports. This way, they disappear from the board immediately but remain part of historical and reporting data.

To create saved filters based on fields like Due Date, Anu needs the ability to view issues in the project. The Browse Projects permission, granted to the Users role, is sufficient for this purpose. It avoids unnecessary access while enabling her to search and filter issues.

To create new components inline, you must have the Administer Projects permission. This permission allows users to manage project configuration elements such as components, versions, and workflows. Granting this permission will enable you to perform the same actions as Vishnu.