Managing Jira Projects for Cloud Free Sample Questions

The Card Colors feature in board settings is specifically designed for this purpose. It allows you to define JQL queries and associate a specific color with the issues that match the query. Swimlanes would separate the issues into horizontal lanes, and Quick Filters would allow users to manually filter the board, neither of which meets the requirement for automatic visual highlighting with a red border.

In a Control Chart, the standard deviation (the shaded area) represents the degree of variance from the average (the solid line). A wide shaded area indicates high variability in the cycle time of issues. This means the process is not predictable, as some issues are completed very quickly while others take a long time, suggesting underlying bottlenecks or inconsistencies in the workflow.

The rule needs to fire when a new issue is created, so this trigger is the correct starting point.

The core requirement is to assign the issue. The 'Edit Issue' action is used to modify fields, including the Assignee field.

The rule must only act under specific circumstances. The Issue Fields Condition can check if 'Component = "Mobile App"' and a JQL condition like 'reporter = email.handler.user' can verify the source, ensuring the rule is correctly targeted.

Configurations in team-managed projects, including workflows, issue types, and custom fields, are self-contained and cannot be shared with other projects. This is a key design difference compared to company-managed projects, where schemes allow for standardized, reusable configurations across multiple projects.

The 'Delete Issues' permission is controlled within the Permission Scheme. To restrict this action, the administrator must grant this permission only to the 'Finance-Managers' project role. The ability to transition issues is controlled by conditions within the workflow, which is part of the Workflow Scheme. The administrator would ensure the workflow transitions do not have conditions that would block other project members.

This query correctly uses the WAS operator with a DURING predicate to find issues that were historically in the specified status during the previous month. It also correctly uses the membersOf() function, which is the proper way to reference a group of users in a JQL query for the assignee field. The other options either check the current status only, use incorrect syntax for group membership, or misuse date functions.

For a sprint to be visible on multiple boards, the issues within that sprint must be visible by each board's filter. If the Phoenix board's filter is project = PHX, it cannot 'see' the sprint container if that sprint also includes issues from the GRF project. To share sprints across boards, the board filters must be inclusive enough to see all issues in the shared sprint, or the sprints will only appear on the board from which they were created and any other boards with compatible filters.

The 'Days in column' indicator does not display for the leftmost column of a Kanban or Scrum board. Jira considers this column the entry point for work on the board, and the timer starts once an issue moves out of this column. To track time for the 'In Progress' status, there must be a column to its left (e.g., 'To Do' or 'Selected for Development').

The 'Browse Projects' permission is the fundamental permission required to see a project and its issues. Without this permission, the project will be completely hidden from the user. They will not see it in dropdowns, on dashboards, or be able to access any of its content, even with a direct URL.

The 'Created vs. Resolved Chart' gadget is specifically designed for this purpose. It generates a line chart showing the number of issues created and resolved over a specified period, making it easy to visualize trends, backlogs, and the team's capacity to handle incoming work.