ACP-620 Questions and Answers

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.

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.

The Time tracking field is required to allow users to enter the number of days (or time) spent and the remaining estimate on issues. Adding this field to theDesignissue type enables tracking of effort in terms of logged and remaining time.

The minimum timeshown is <1 minute, which indicates the fastest an issue transitioned to done.

The average time shown is 1w 13h 17m, which confirms that on average, issues take over oneweek to complete.

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 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.

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 thepast and may or may not still be.

When multiple components are selected on issue creation, Jira cannot determine a singledefault assignee if each component has a different assignee rule. In this case:

● Hardware → Component lead (Vincent Choy)

● Software → Project default (Alana Grant)

● Infrastructure → Unassigned

Since the assignee logic conflicts, Jira defaults to Unassigned to avoid ambiguity.

Created vs. Resolved Issues Report: This report depends on the Resolved status to track when issues are considered resolved. Removing the status may impact the accuracy of this report.

Column mapping on the project board: If Resolved was previously mapped to a column, you must update the board’s column mapping to reflect the workflow change and prevent unmapped statuses.

Project administrators can use automation rules to send customized emails during workflow transitions. This allows targeted communication to various groups without needing global admin rights, which are required for modifying notification schemes or installing apps.

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.