Users have been adding sensitive information into the Description field of issues in a particular project. You must secure the project by any means necessary so that only members of the Managers group can view the contents of the Description field. Which approach will definitively satisfy this requirement? (Choose one)
Correct Answer: C
Question 22
You run the JQL query shown: assignee changed from currentUser() TO EMPTY and resolution changed to EMPTY Which statement is definitely true?
Correct Answer: C
The JQL query assignee changed from currentUser() TO EMPTY and resolution changed to EMPTY filters for issues based on their change history for theassigneeandresolutionfields. The statement that is definitely true isall returned issues were assigned to you at some point(Option C), as the query explicitly requires that theassigneefield changed from the current user toEMPTY. * Explanation of the Correct Answer (Option C): * The query consists of two conditions: * assignee changed from currentUser() TO EMPTY: This means the issue'sassigneefield was changed from the current user (the person running the query) tounassigned(EMPTY) at some point in its history. For this condition to be true, the issue must have been assigned to the current user before being unassigned. * resolution changed to EMPTY: This means theresolutionfield was changed toEMPTY (unresolved) at some point, typically indicating the issue was reopened (e.g., resolution was cleared). * Theassignee changed from currentUser() TO EMPTYcondition guarantees that all returned issues were assigned to the current user at some point, as the change history explicitly includes a transition from the current user to unassigned. * Exact Extract from Documentation: Advanced searching - operators reference TheCHANGEDoperator searches for issues where a field's value changed from one value to another. * assignee changed from currentUser() TO EMPTY: Finds issues where the assignee was changed from the current user to unassigned. * resolution changed to EMPTY: Finds issues where the resolution was cleared (e.g., issue was reopened).Note: TheCHANGEDoperator examines the issue's history, not its current state.(Source: Atlassian Support Documentation, "Advanced searching - operators reference") * Why This Fits: The query's conditionassignee changed from currentUser() TO EMPTY ensures that all returned issues were assigned to the current user at somepoint, making Option C definitely true. * Why Other Options Are Incorrect: * All returned issues are currently unresolved (Option A): * Theresolution changed to EMPTYcondition means the resolution was set toEMPTYat some point in the issue's history, but the issue could have been resolved again later (e.g., resolution set to Done). The query does not check the current resolution state, so this is not definitely true. * Extract from Documentation: TheCHANGEDoperator does not guarantee the current state of a field. Use resolution is EMPTY to check if issues are currently unresolved. (Source: Atlassian Support Documentation, "Advanced searching - operators reference") * All returned issues are currently unassigned (Option B): * Theassignee changed from currentUser() TO EMPTYcondition means the issue was unassigned at some point, but it could have been reassigned to another user later. The query does not check the current assignee state, so this is not definitely true. * Extract from Documentation: To check if issues are currently unassigned, use assignee is EMPTY. TheCHANGEDoperator only checks historical changes. (Source: Atlassian Support Documentation, "Advanced searching - fields reference") * All returned issues are currently not assigned to you (Option D): * The query does not guarantee that issues are currently not assigned to the current user. After being unassigned (TO EMPTY), the issue could have been reassigned to the current user again. The current assignee state is not checked, so this is not definitely true. * Extract from Documentation: TheCHANGEDoperator does not reflect the current field value. Use assignee != currentUser() to check if issues are not assigned to the current user. (Source: Atlassian Support Documentation, "Advanced searching - operators reference") * All returned issues were in Done status at some point (Option E): * Theresolution changed to EMPTYcondition indicates the resolution was cleared (e.g., issue reopened), which often follows a resolved state (e.g., Done). However, the query does not explicitly require that the issue was in aDonestatus (or had a resolution set) before the change toEMPTY. For example, an issue could have had a resolution set to another value or cleared without being inDone. Thus, this is not definitely true. * Extract from Documentation: Theresolution changed to EMPTYcondition indicates a resolution was cleared, but it does not guarantee the issue was in a specific status like Done. (Source: Atlassian Support Documentation, "Advanced searching - fields reference") * Additional Notes: * The query examines historical changes, not current states, so assumptions about currentresolution orassigneevalues are invalid. * To ensure current states, additional conditions like resolution is EMPTY or assignee is EMPTY would be needed. * The query requires the user to haveBrowse Projectspermission for the relevant projects. : Atlassian Support Documentation:Advanced searching - operators reference Atlassian Support Documentation:Advanced searching - fields reference Atlassian Support Documentation:Search for issues using JQL
Question 23
A dashboard displays an Issue Statistics gadget as shown. The dashboard owner wants to change the order of the statuses shown in the gadget to appear as follows. 1. To Do 2. In Progress 3. Ready For QA 4. Blocked 5. Rejected 6. Done Which action will permanently arrange the statuses into the required order?
No one should be allowed to edit issues in a particular workflow status of a company-managedproject. Which element must be configured?
Correct Answer: D
Okay, let's analyze this question again with the revised options. The requirement is to preventanyonefromeditingan issue when it resides in aspecific workflow status. As established previously: * Conditions (A):Control whether atransitionout of or into a status can occur. They check criteriabeforea transition starts. They don't prevent editingwhilean issue is sitting in a status. * Post Functions (Implied by B & C):Actions that executeaftera transition is successfully completed (e. g., updating a field, sending a notification). They don't affect editability within the status itself. * Triggers (D):Automatically initiate a workflow transition based on external events (like code commits). Not relevant to editing permissions within a status. The correct way to achieve this in Jira is by setting aStatus Property: * Navigate to Workflow configuration. * Select the relevant status. * Go to its 'Properties'. * Add a property: jira.issue.editable with the value false.
Question 25
Your organization uses Jira Software and Confluence. Dave is a new employee who needs the following privileges * Approve access requests * Manage group memberships * Update billing details You need to give him enough but not too many privileges How should you configure Dave's user account? (Choose one)
