ACP-620 Managing Jira Projects for CloudExam Questions and Answers

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.

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.

A Kanban board without backlog displays all issues on a single view and supports a continuous workflow without start and stop dates. This setup is ideal for teams using a continuous delivery process, allowing issues to move freely across the entire workflow.

The error "The filter configured for this gadget could not be retrieved" typically means that the filters used in the dashboard gadgets are not shared with Bobby. Even if Bobby has access to the projects or issues, he cannot see the results unless the filters themselves are explicitly shared with him.

The Velocity Chart shows the amount of story points completed in each sprint, allowing you to determine the average effort the team can deliver. It's specifically designed to track estimation units like story points across completed sprints.

Card colors by priority: Visually distinguishes issue cards on the board based on their priority.

Swimlanes by epic: Groups all issues under their respective epics, helping the team see work organized by feature or theme.

Quick filters based on radio button field: Allows team members to filter and view specific subsets of issues depending on the selected radio button field value.

Create a new Scrum board that includes both MOBI and TIS issues: This allows the teams to plan and manage sprints using a single board that pulls issues from both projects.

Change the TIS project board filter to include issues from MOBI project: Modifying the board filter to include issues from both projects enables the board to support a shared sprint across MOBI and TIS.

Bulk operations: Allow assigning multiple issues at once without manual assignment of each individual issue.

Project default assignment: Automatically assigns new issues to a default user (e.g., Project Lead).

Component lead assignment: Assigns issues based on the lead of the selected component.

Automation rules: Automatically assign issues based on conditions such as issue type, priority, or custom field values.

Modifying the board sub-filter allows you to excludeDoneissues 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.

In team-managed projects, field settings for paragraph fields include a toggle to allow or prevent @ mentions. If users can enter text but not @ mention others, it’s likely that the mention functionality is disabled in the field configuration.

The user condition is checking whether the reporter is in the Executives group, but the rule is triggered when the issue is commented on. To work as intended, the condition should check whether the commenter (i.e., user who triggered the rule) is in the Executives group - not the reporter.

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.

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.