You need to create a filter that shows only issues that were created during the last calendar month. Identify the correct JQL query.
created changed during (startOfMonth(), endOfMonth())
createdDate >= startOfMonth(-1) OR createdDate <= endOfMonth(-1)
created >= startOfMonth(-1) AND created <= endOfMonth(-1)
createdDate >= startOfMonth(-1m) AND createdDate <= endOfMonth(-1m)
To create a filter that shows issues created during the last calendar month, the JQL query must use thecreatedDatefield with thestartOfMonth(-1m)andendOfMonth(-1m)functions to define the time range. The correct query iscreatedDate >= startOfMonth(-1m) AND createdDate <= endOfMonth(-1m)(Option D).
Explanation of the Correct Answer (Option D):
ThecreatedDatefield represents the date an issue was created. ThestartOfMonth(-1m)function returns the first day of the previous month (e.g., April 1, 2025, for May 2025), andendOfMonth(-1m)returns the last day of the previous month (e.g., April 30, 2025). The querycreatedDate >= startOfMonth(-1m) AND createdDate <= endOfMonth(-1m)selects issues created within this range, covering the entire last calendar month.
Exact Extract from Documentation:
Search for issues using JQL
ThecreatedDatefield (orcreatedalias) stores the creation date of an issue. Use date functions likestartOfMonth()andendOfMonth()to define time ranges.
Examples:
createdDate >= startOfMonth(-1m) AND createdDate <= endOfMonth(-1m) returns issues created in the previous calendar month.
Use-1mto indicate one month ago.Note: Ensure date fields use>=and<=for inclusive ranges.(Source: Atlassian Support Documentation, "Search for issues using JQL")
Why This Fits: The query in Option D correctly usescreatedDate,startOfMonth(-1m), andendOfMonth(-1m)withANDto define the last calendar month, making it the correct answer.
Why Other Options Are Incorrect:
created changed during (startOfMonth(), endOfMonth()) (Option A):
Thechanged duringoperator is used for fields that track changes (e.g., status, assignee), not for static fields likecreated. Additionally,startOfMonth()andendOfMonth()without-1mrefer to the current month, not the last month.
Extract from Documentation:
Thechanged duringoperator is invalid for thecreatedfield. Use>=and<=for date comparisons.
(Source: Atlassian Support Documentation, "Advanced searching - operators reference")
createdDate >= startOfMonth(-1) OR createdDate <= endOfMonth(-1) (Option B):
TheORoperator creates a logical error, selecting issues created after the start of the previous monthorbefore the end of the previous month, which includes almost all issues. Additionally,-1is ambiguous and typically invalid without a unit (e.g.,-1mfor one month). The correct operator isANDto define a range.
Extract from Documentation:
UseANDto define a date range (e.g., createdDate >= startOfMonth(-1m) AND createdDate <= endOfMonth(-1m)).ORcreates an overly broad range.
(Source: Atlassian Support Documentation, "Advanced searching - operators reference")
created >= startOfMonth(-1) AND created <= endOfMonth(-1) (Option C):
The-1syntax without a unit (e.g.,-1m) is ambiguous and typically invalid in JQL. The correct syntax uses-1mto indicate one month ago. Additionally, whilecreatedis an alias forcreatedDate, the incorrect time unit makes this query invalid.
Extract from Documentation:
Date functions require units likemfor months (e.g.,startOfMonth(-1m)). Without a unit, the query is invalid.
(Source: Atlassian Support Documentation, "Advanced searching - functions reference")
Additional Notes:
The filter can be created inIssues > Search for issues, saved as a filter, and shared if needed.
Thecreatedalias can be used instead ofcreatedDate, butcreatedDateis more explicit and matches the options.
Ensure the Jira instance’s timezone aligns with the expected month range.
An automation rule should send an email with the issue key in the subject line. Identify the correct syntax to use in the Send Email action.
{{triggerIssue.issuekey}}
{{issue.key}}
{{issueKey}}
{issue.issuekey}
issue.key
In Jira Software Cloud, automation rules usesmart valuesto reference issue fields, such as the issue key, in actions like sending emails. The correct syntax for referencing the issue key in theSend Emailaction’s subject line is{{issue.key}}(Option B).
Explanation of the Correct Answer (Option B):
The{{issue.key}}smart value retrieves the issue key (e.g., PROJ-123) of the issue that triggers or is processed by the automation rule. This can be used in the subject line of theSend Emailaction to include the issue key dynamically.
Exact Extract from Documentation:
Use smart values in automation rules
Smart values allow you to access issue fields and other data in automation actions. To reference the issue key:
Use{{issue.key}}to insert the issue key (e.g., PROJ-123) in fields like email subjects or bodies.Examples:
Email subject: Issue {{issue.key}} Updated
Output: Issue PROJ-123 UpdatedNote: Smart values are enclosed in double curly braces ({{}}). Use dotnotation to access fields (e.g., {{issue.key}}, {{issue.summary}}).(Source: Atlassian Support Documentation, "Use smart values in Jira automation")
Why This Fits: The{{issue.key}}syntax is the standard way to reference the issue key in Jira automation, making it the correct choice for theSend Emailaction’s subject line.
Why Other Options Are Incorrect:
{{triggerIssue.issuekey}} (Option A):
The{{triggerIssue}}smart value refers to the issue that triggers the rule, but the field iskey, notissuekey. The correct syntax is{{triggerIssue.key}}, not{{triggerIssue.issuekey}}. Additionally,{{issue.key}}is sufficient for most rules unless specifically targeting the trigger issue in a branched rule.
Extract from Documentation:
Use{{triggerIssue.key}}to reference the key of the issue that triggers the rule.{{issue.key}}is used for the current issue in the rule’s context.
(Source: Atlassian Support Documentation, "Use smart values in Jira automation")
{{issueKey}} (Option C):
Smart values require dot notation for field access (e.g.,{{issue.key}}).{{issueKey}}is not a valid smart value, as it does not reference a specific field.
Extract from Documentation:
Smart values must reference valid fields using dot notation (e.g., {{issue.key}}, {{issue.summary}}). Single variables like {{issueKey}} are not supported.
(Source: Atlassian Support Documentation, "Use smart values in Jira automation")
{issue.issuekey} (Option D):
The syntax uses single curly braces andissuekeyinstead ofkey, which is incorrect. Smart values require double curly braces ({{}}) and the correct field name (key).
Extract from Documentation:
Smart values use double curly braces ({{}}) and standard field names (e.g., {{issue.key}}). Incorrect formats like {issue.issuekey} will not work.
(Source: Atlassian Support Documentation, "Use smart values in Jira automation")
issue.key (Option E):
Without curly braces,issue.keyis treated as plain text, not a smart value. It will not resolve to the issue key and will appear literally in the email subject.
Extract from Documentation:
Smart values must be enclosed in {{}} to be evaluated. Plain text like issue.key will not resolve to a field value.
(Source: Atlassian Support Documentation, "Use smart values in Jira automation")
Additional Notes:
TheSend Emailaction in Jira automation allows smart values in the subject and body to dynamically include issue data.
If the rule involves branching or multiple issues,{{issue.key}}refers to the current issue in the rule’s context, while{{triggerIssue.key}}refers to the triggering issue. For a simple email rule,{{issue.key}}is typically sufficient.
All company-managed projects share the same permission scheme and workflow scheme. New requirements state:
• Only auditors should be able to use the 'Needs Audit' workflow transition.
• All auditors work across all the projects.
How should auditors be configured?
As a User custom field
As a group
As a Group custom field
As single users
To restrict theNeeds Auditworkflow transition to auditors across all company-managed projects, which share the same permission and workflow schemes, auditors should be configuredas a group(Option B). This allows the group to be referenced in a workflow condition to limit access to the transition efficiently across all projects.
Explanation of the Correct Answer (Option B):
The requirement to restrict theNeeds Audittransition to auditors can be achieved by adding aconditionto the transition in the shared workflow scheme. A common condition, such asUser Is In Group, restricts the transition to members of a specific group.
Since all projects share the same workflow scheme, configuring auditors as a group (e.g., “Auditors”) allows you to create the group once, add all auditors to it, and reference it in the workflow condition. This ensures that only auditors can use theNeeds Audittransition across all projects.
Exact Extract from Documentation:
Configure workflow conditions
Conditions restrict who can perform a workflow transition in a company-managed project.
To restrict a transition:
Go toSettings > Issues > Workflows.
Edit the workflow and select theNeeds Audittransition.
Add a condition, such asUser Is In Group, and select the group (e.g., Auditors).Note: Using a group is efficient for managing permissions or conditions across multiple projects with a shared workflow scheme.(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
Why This Fits: Configuring auditors as a group allows a single workflow condition to restrict theNeeds Audittransition to group members across all projects, meeting both requirements efficiently.
Why Other Options Are Incorrect:
As a User custom field (Option A):
AUser custom field(e.g., User Picker) stores a single user for an issue and is not suitable for defining a set of users who can perform a workflow transition. Workflow conditions cannot reference custom fields to restrict transitions.
Extract from Documentation:
User custom fields store user data for issues but cannot be used in workflow conditions to restrict transitions.
(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
As a Group custom field (Option C):
AGroup custom field(e.g., Group Picker) stores a group for an issue, but workflow conditions typically reference groups directly, not group picker fields. This approach is unnecessary and overly complex for restricting transitions.
Extract from Documentation:
Group custom fields are not used for workflow conditions. Use direct group references for transition restrictions.
(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
As single users (Option D):
Configuring auditors as individual users in a workflow condition (e.g.,User Is In Any Users) is inefficient, as it requires listing each auditor manually. This approach does not scale well for multiple auditors working across all projects and is prone to maintenance issues if auditors change.
Extract from Documentation:
Listing individual users in conditions is not recommended for scalability. Use groups for managing multiple users across projects.
(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
Additional Notes:
Steps to configure:
Create an “Auditors” group inSettings > User management > Groups.
Add all auditors to the “Auditors” group.
Edit the shared workflow inSettings > Issues > Workflows.
Add aUser Is In Groupcondition to theNeeds Audittransition, selecting the “Auditors” group.
Configuring the group and workflow requiresJira administratorprivileges.
The shared workflow scheme ensures the condition applies to all projects.
You are configuring an issue layout in a company-managed project. Which statement is true?
You can reuse fields from a team-managed project.
You can copy a layout to another project using the same screen.
You can move any field to the Hidden fields section.
You can move any field to the Context fields section.
In a company-managed project, theissue layoutdetermines how fields are displayed in the issue view (e.g., which fields are visible, hidden, or in the context panel). The true statement is thatyou can copy a layout to another project using the same screen(Option B), as Jira allows copying issue layouts to streamline configuration across projects.
Explanation of the Correct Answer (Option B):
Theissue layoutin a company-managed project is configured inProject settings > Issue layoutand is tied to a screen (via the screen scheme). Jira allows copying an issue layout to another project that uses the same screen, ensuring consistent field arrangements across projects.
Exact Extract from Documentation:
Configure issue layouts in company-managed projects
Issue layouts define which fields are displayed, hidden, or placed in the context panel in the issue view.
To copy a layout:
Go toProject settings > Issue layout.
SelectCopy layoutand choose another project that uses the same screen.Note: The target project must use the same screen (via its screen scheme) for the layout to be compatible.(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
Why This Fits: Copying an issue layout to another project using the same screen is a supported feature, making Option B the correct answer.
Why Other Options Are Incorrect:
You can reuse fields from a team-managed project (Option A):
Fields in team-managed projects are project-specific and cannot be reused in company-managed projects. Company-managed projects use global custom fields or system fields, managed inSettings > Issues > Custom fields. Fields from team-managed projects are isolated and not accessible.
Extract from Documentation:
Custom fields in team-managed projects are project-specific and cannot be reused in company-managed projects. Company-managed projects use global custom fields.
(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
You can move any field to the Hidden fields section (Option C):
Not all fields can be moved to theHidden fieldssection. System fields likeSummary,Issue Type, andStatusare required and cannot be hidden. Only non-mandatory fields (e.g., custom fields, non-required system fields) can be hidden.
Extract from Documentation:
In the issue layout, you can hide non-mandatory fields by moving them to theHidden fieldssection. Required fields like Summary, Issue Type, and Status cannot be hidden.
(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
You can move any field to the Context fields section (Option D):
TheContext fieldssection (right panel in the issue view) has restrictions on which fields can be placed there. Fields likeSummary,Description, and certain system fields cannot be moved to the context panel, as they are designed for the main issue view. Only eligible fields (e.g., custom fields, Labels, Components) can be moved to theContext fieldssection.
Extract from Documentation:
TheContext fieldssection is for fields like Labels, Components, or custom fields. Core fields like Summary and Description cannot be moved to the context panel.
(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
Additional Notes:
Configuring issue layouts requiresproject adminprivileges for the project (Project settings > Issue layout).
Copying layouts is useful for maintaining consistency across projects with similar configurations.
You are configuring an issue type screen in a team-managed project. Which statement is true?
You can edit the name of any field on the screen.
You can reuse a custom field from another team-managed project.
You can add any field type to the Context fields section.
You can add any field type to the Description fields section.
You can reorder custom fields within all sections of the screen.
In a team-managed project, theissue type screen(configured inProject settings > Issue types) determines which fields are displayed for an issue type and how they are organized (e.g., in sections like Description or Context fields). The true statement is thatyou can reorder custom fields within all sections of the screen(Option E), as team-managed projects allow flexible reordering of fields within their designated sections.
Explanation of the Correct Answer (Option E):
In team-managed projects, the issue type screen is configured per issue type, and fields (including custom fields) are organized into sections (e.g., Description fields, Context fields). Users with appropriate permissions (e.g., project admins) can reorder custom fields within any section of the screen to customize the layout, ensuring fields appear in the desired order for creation, editing, or viewing.
Exact Extract from Documentation:
Configure issue types in team-managed projects
Each issue type in a team-managed project has its own screen configuration, defining which fields are displayed and their order.
To reorder fields:
Go toProject settings > Issue types.
Select the issue type and edit its screen.
Drag and drop fields (including custom fields) within sections (e.g., Description fields, Context fields) to reorder them.Note: Custom fields can be reordered within any section of the screen, but some system fields have fixed positions.(Source: Atlassian Support Documentation, "Configure issue types in team-managed projects")
Why This Fits: The ability to reorder custom fields within all sections of the issue type screen is a standard feature in team-managed projects, making Option E the true statement.
Why Other Options Are Incorrect:
You can edit the name of any field on the screen (Option A):
In team-managed projects, you cannot edit the name of fields directly on the screen configuration. Custom field names are set when the field is created (Project settings > Project fields), and system field names (e.g., Summary, Description) are fixed. The screen configuration only allows adding, removing, or reordering fields, not renaming them.
Extract from Documentation:
Field names are set inProject settings > Project fieldsfor custom fields or are fixed for system fields. Screen configurations do not allow renaming fields.
(Source: Atlassian Support Documentation, "Manage fields in team-managed projects")
You can reuse a custom field from another team-managed project (Option B):
Custom fields in team-managed projects are project-specific and cannot be reused across projects, unlike company-managed projects where global custom fields are shared. To use a similar field, you must create a new custom field in the project.
Extract from Documentation:
Custom fields in team-managed projects are unique to the project and cannot be reused from other team-managed projects.
(Source: Atlassian Support Documentation, "Manage fields in team-managed projects")
You can add any field type to the Context fields section (Option C):
TheContext fieldssection (right panel in the issue view) has restrictions on which field types can be added. System fields likeSummary,Description, and certain others are fixed in the main section and cannot be moved to the Context fields section. Only eligible fields (e.g., custom fields, Labels, Components) can be added to this section.
Extract from Documentation:
TheContext fieldssection is limited to certain field types (e.g., custom fields, Labels). Core fields like Summary and Description cannot be moved to Context fields.
(Source: Atlassian Support Documentation, "Configure issue types in team-managed projects")
You can add any field type to the Description fields section (Option D):
TheDescription fieldssection (main section below the Summary) also has restrictions. Fields likeSummary,Issue Type, andStatusare fixed in their positions, and not all field types can be added to the Description fields section. Only certain fields (e.g., Description, custom text fields) are eligible.
Extract from Documentation:
TheDescription fieldssection is for fields like Description or custom text fields. Some system fields have fixed positions and cannot be moved.
(Source: Atlassian Support Documentation, "Configure issue types in team-managed projects")
Additional Notes:
Configuring issue type screens requiresproject adminprivileges in a team-managed project (Project settings > Issue types).
Reordering fields enhances usability by prioritizing important fields in each section.
System fields may have limited reordering options compared to custom fields.
You want to create a new link type that looks identical in linked issues. How can you achieve this?
Create the link type with no inward link description.
Disable bidirectional linking globally.
Choose the same name for the inward and outward link descriptions.
Create the link type with no outward link description.
To create a new link type in Jira Software Cloud that looks identical in linked issues (i.e., the link description is the same regardless of the direction of the link), you shouldchoose the same name for the inward and outward link descriptions(Option C). This ensures that the link type appears with the same description in both the source and target issues.
Explanation of the Correct Answer (Option C):
In Jira,issue link typesdefine relationships between issues, with anoutwarddescription(for the source issue) and aninward description(for the target issue). For example, a “Blocks” link type might have “blocks” as the outward description and “is blocked by” as the inward description. To make the link type look identical in both linked issues, you set the same description for both the inward and outward links (e.g., “relates to” for both). This results in the link appearing as “relates to” in both issues, regardless of which issue is the source or target.
Exact Extract from Documentation:
Manage issue link types
Issue link types define relationships between issues, with separateoutwardandinwarddescriptions.
To create a link type:
Go toSettings > Issues > Issue linking.
Add a new link type.
Enter aName(e.g., Relates), and set theOutward descriptionandInward description(e.g., both as “relates to”).Impact: If the inward and outward descriptions are the same, the link appears identical in both linked issues.Note: Requires Jira administrator permissions.(Source: Atlassian Support Documentation, "Configure issue linking in Jira Cloud")
Why This Fits: Setting the same name for the inward and outward link descriptions ensures the link type looks identical in linked issues, meeting the requirement and making Option C the correct answer.
Why Other Options Are Incorrect:
Create the link type with no inward link description (Option A):
Jira requires both aninwardandoutwarddescription when creating a link type. Leaving the inward description blank is not allowed, and even if possible, it would not make the link look identical in both issues—it would result in an empty or default description in the target issue.
Extract from Documentation:
Bothinwardandoutwarddescriptions are required when creating a link type. Blank descriptions are not supported.
(Source: Atlassian Support Documentation, "Configure issue linking in Jira Cloud")
Disable bidirectional linking globally (Option B):
There is no concept ofbidirectional linkingin Jira’s issue linking system, and no global setting exists to disable it. Issue links are inherently bidirectional (a link from issue A to B implies a reverse link from B to A), and the descriptions control how they appear. Disabling linking is not an option.
Extract from Documentation:
Issue links are bidirectional, with inward and outward descriptions defining the relationship. No global setting exists to disable bidirectionality.
(Source: Atlassian Support Documentation, "Configure issue linking in Jira Cloud")
Create the link type with no outward link description (Option D):
Similar to Option A, Jira requires anoutwarddescription when creating a link type. Leaving it blank is not allowed, and it would not achieve identical appearance in both issues, as the source issue would lack a description.
Extract from Documentation:
Bothoutwardandinwarddescriptions are mandatory for issue link types.
(Source: Atlassian Support Documentation, "Configure issue linking in Jira Cloud")
Additional Notes:
Steps to configure:
Go toSettings > Issues > Issue linking.
ClickAdd link type.
Enter aName(e.g., “Relates”) and set bothOutward descriptionandInward descriptionto the same value (e.g., “relates to”).
Save the link type.
Configuring issue link types requiresJira administratorprivileges.
The new link type will appear identically in both linked issues (e.g., “Issue A relates to Issue B” and “Issue B relates to Issue A”).
Currently, users log time and enter a comment on a transition screen when closing issues. Now, they want the comment to be copied automatically to the work log description. Identify the configuration area that needs to be modified.
Field configuration
Global time tracking settings
Issue layout
Workflow condition
Global permissions
The requirement involves automating an action during a workflow transition (copying a comment entered on a transition screen to the work log description when closing issues). As correctly noted, this type of automation is typically handled by aworkflow post function, which executes actions after a transition is completed. However, the provided options do not include "workflow post function." Among the options,Workflow condition(Option D) is the closest, as it points to the general area of workflow configuration where post functions are also managed, despite being technically inaccurate since conditions and post functions serve different purposes. Let’s analyze this in detail.
Explanation of the Correct Approach (Workflow Post Function):
Aworkflow post functionis the appropriate mechanism to copy the comment entered on the transition screen to the work log description during theClose Issuetransition. Post functions are executed automatically after a transition completes, and they can manipulate issue data, such as copying field values. However, Jira’s out-of-the-box post functions (e.g.,Copy Value From Other Field) may not directly support copying a transition screen comment to a work log description, as the comment field on a transition screen is transient and not stored as a standard issuefield until the transition is complete. This may require a custom post function or a third-party app (e.g., ScriptRunner) to script the behavior.
Alternatively, aJira automation rulecould achieve this by triggering on theIssue Transitionedevent (to the Closed status) and copying the latest comment to the work log description, but automation rules are configured separately and not part of the workflow editor.
Exact Extract from Documentation:
Configure workflow post functions
Post functions are executed after a transition is completed and can perform actions like updating fields or copying data.
To configure:
Go toSettings > Issues > Workflows.
Edit the workflow and select theClose Issuetransition.
Add a post function (e.g.,Copy Value From Other Fieldor a scripted post function via an app).Note: Copying a transition screen comment to a work log description may require a custom script or third-party app, as standard post functions do not directly support this.(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
Why This Fits the Requirement: A post function on theClose Issuetransition can automate the copying of the comment to the work log description, aligning with the requirement for an action during a workflow transition.
Analysis of the Options and Selection of Option D:
The options provided do not include "workflow post function," which is the precise configuration area. However, let’s evaluate each option:
Field configuration (Option A):
Field configurationscontrol whether fields are required, optional, or hidden for specific issue types. They do not handle automation or copying data between fields during transitions.
Extract from Documentation:
Field configurations manage field behavior (required, hidden), not field value copying or automation.
(Source: Atlassian Support Documentation, "Configure field settings")
Global time tracking settings (Option B):
Global time tracking settingsconfigure time tracking formats, permissions, and defaults (e.g., enabling time logging, setting time units). They do not control copying data between fields like comments and work log descriptions.
Extract from Documentation:
Global time tracking settings manage time tracking behavior, not field interactions or automation.
(Source: Atlassian Support Documentation, "Configure time tracking in Jira Cloud")
Issue layout (Option C):
Issue layoutsdetermine field visibility and arrangement in the issue view (e.g., which fields are shown or hidden). They do not manage automation or data copying during transitions.
Extract from Documentation:
Issue layouts control field display in the issue view, not field value copying or automation.
(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
Workflow condition (Option D):
Workflow conditionsrestrict who can perform a transition (e.g., only users in a specific group). They do not execute actions like copyingdata between fields, which is the role of apost function. However, both conditions and post functions are configured within the same workflow editor (under the transition settings), makingWorkflow conditionthe closest option to the general area of workflow configuration where post functions reside. The question’s options may reflect a terminology error, intending "workflow post function" but listing "workflow condition" instead. Given the context of a workflow transition action, Option D is the most plausible choice despite the inaccuracy.
Extract from Documentation:
Conditions restrict transition access, while post functions perform actions like updating fields. Both are configured in the workflow editor under the transition settings.
(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
Global permissions (Option E):
Global permissionscontrol system-wide actions (e.g., Administer Jira, Work On Issues). They do not manage field interactions or automation during transitions.
Extract from Documentation:
Global permissions manage system access, not field automation or workflow actions.
(Source: Atlassian Support Documentation, "Manage global permissions")
Why Option D is Selected: WhileWorkflow conditionis technically incorrect (as conditions do not copy data), it points to the workflow configuration area where the correct solution—apost function—is implemented. In the absence of a "workflow post function" option, Option D is the closest match, likely due to a wording error in the question. The user’s analysis aligns with this interpretation, recognizing that the solution lies within the workflow editor, specifically with post functions.
Additional Notes:
Steps to Configure a Post Function:
Go toSettings > Issues > Workflows(requires Jira administrator privileges).
Edit the workflow used by the project and select theClose Issuetransition.
Add a post function to copy the transition screen comment to the work log description (this may require a custom script or third-party app like ScriptRunner, as standard post functions do not directly support this).
Alternative with Automation Rule:
Go toProject settings > Automation(orSettings > System > Automation rulesfor global rules).
Create a rule with the triggerIssue Transitioned(to Closed status).
Add a condition to check for a new comment (if needed).
Add an action to edit the work log and copy the latest comment to the work log description (may require scripting or app support).
The question’s options suggest a possible oversight in not including "workflow post function." However, interpretingWorkflow conditionas a reference to the broader workflow configuration area (where post functions are managed) makes it the most reasonable choice.
In a company-managed project, a limited set of users should be notified when issues transition to Pending status, and the project admin must be able to manage the list of users. What two items must be configured? (Choose two.)
Project role
Workflow condition
Custom event
Workflow validator
Group
To address the requirement of notifying a limited set of users when issues transition to a "Pending" status in a company-managed project, and allowing the project admin to manage the list of users, two key configurations are necessary: aproject roleand acustom event. Below is the detailed explanation based on official Jira Software Cloud documentation.
Project Role (Option A):
Purpose: Project roles allow project administrators to define and manage a group of users who can be assigned specific permissions or notification responsibilities within a project. This is critical for the requirement that the project admin must manage the list of users to be notified.
How It Works: In Jira, project roles (e.g., "Developers," "Administrators," or a custom role like "Pending Status Notifiers") are created and managed at the project level. The project admin can add or remove users from these roles without needing global admin permissions, which aligns with the requirement for the project admin to manage the user list.
Configuration Steps:
Navigate toProject Settings > Peoplein the company-managed project.
Create a new project role or use an existing one (e.g., "Pending Notifiers").
Add users to this role as needed. The project admin can update this list at any time.
In the notification scheme, associate the project role with the custom event (explained below) to ensure that users in this role receive notifications when the event is triggered.
Why This Is Necessary: Using a project role ensures scalability and flexibility. Instead of hardcoding individual users or groups in the notification scheme, a project role allows the admin to dynamically manage who receives notifications without modifying the underlying configuration.
Custom Event (Option C):
Purpose: A custom event is required to trigger notifications specifically for thetransition to the "Pending" status. Jira’s notification system relies on events to determine when and to whom notifications are sent. By creating a custom event, you can link it to the specific workflow transition (e.g., moving to "Pending") and configure the notification scheme to notify the project role.
How It Works: In Jira, events are fired during workflow transitions via post functions. A custom event (e.g., "Issue Moved to Pending") can be created and associated with the transition to the "Pending" status. The notification scheme is then configured to send notifications to the designated project role when this event occurs.
Configuration Steps:
Navigate toSettings > System > Events(requires Jira admin permissions).
Create a new custom event, such as "Issue Moved to Pending," with a description and an appropriate notification template (e.g., "Issue Updated").
In the workflow used by the project, edit the transition to the "Pending" status:
Add a post function to the transition, such as"Fire a Generic Event"or a custom event, and select the custom event ("Issue Moved to Pending").
Update the project’snotification scheme(found inProject Settings > NotificationsorSettings > Issues > Notification Schemes):
Map the custom event to the project role (e.g., "Pending Notifiers") to ensure that users in this role receive notifications when the event is fired.
Why This Is Necessary: A custom event is essential because Jira’s default events (e.g., "Issue Updated," "Issue Created") may not be specific enough to target only the "Pending" status transition. A custom event ensures that notifications are sent only when the issue transitions to "Pending," meeting the requirement for targeted notifications.
Why Other Options Are Incorrect:
Workflow Condition (Option B):
A workflow condition controls whether a user can execute a transition (e.g., restricting who can move an issue to "Pending"). It does not influence notifications or manage lists of users to be notified. Therefore, it is irrelevant to the requirement of notifying users and allowing the project admin to manage the user list.
Workflow Validator (Option D):
A workflow validator checks whether certain criteria are met before allowing a transition to proceed (e.g., ensuring a field is filled). Like conditions, validators do not handle notifications or user management for notifications, making this option incorrect.
Group (Option E):
While groups can be used in notification schemes to define who receives notifications, they are managed by Jira admins at the global level (viaSettings > User Management > Groups), not by project admins. The requirement specifies that theproject adminmust manage the list of users, which is not feasible with groups since project admins lack permission to edit global groups. Project roles, however, can be managed by project admins, making them the correct choice over groups.
Additional Notes:
The configuration assumes a company-managed project, as team-managed projects have simpler permission and notification settings that do not support custom events or complex workflow configurations to the same extent.
If the project admin lacks permission to edit workflows or notification schemes (which require Jira admin access), they would need to collaborate with a Jira admin to set up the custom event and initial notification scheme. However, once configured, the project admin can manage the project role’s membership independently.
The use of a custom event ensures that notifications are specific to the "Pending" status transition, avoiding unnecessary notifications for other transitions or actions.
The Customer Relations team has just been given access to Jira. They can see two projects but not the project boards. They created several advanced searches and want other project members to see the results. Which permission do they require without receiving too much access?
Browse Projects
Share dashboards and filters
Board administrator
Administer Jira
The Customer Relations team can see two projects (indicating they haveBrowse Projectspermission) but not the project boards, and they want to share advanced searches (filters) with other project members. The permission required to share filters without granting excessive access is theShare dashboards and filtersglobal permission (Option B).
Explanation of the Correct Answer (Option B):
TheShare dashboards and filtersglobal permission allows users to share filters and dashboards with other users, groups, or roles. This permission is necessary for the team to make their advanced searches visible to other project members. It is a targeted permission that does not grant additional administrative or project-level access.
Exact Extract from Documentation:
Share dashboards and filters permission
TheShare dashboards and filtersglobal permission allows users to share filters and dashboards with other users, groups, projects, or the entire organization.
To grant this permission:
Go toSettings > System > Global permissions.
Add a user, group, or role to theShare dashboards and filterspermission.Note: This permission is required to make filters or dashboards accessible to others, but it does not grant access to view issues or manage boards.(Source: Atlassian Support Documentation, "Manage global permissions")
Why This Fits: TheShare dashboards and filterspermission directly enables the team to share their advanced searches (filters) with other project members without granting unnecessary privileges, making Option B the correct choice.
Why Other Options Are Incorrect:
Browse Projects (Option A):
TheBrowse Projectspermission allows users to view issues in a project. Since the team can already see two projects, they likely have this permission. It does not control the ability to share filters or access project boards.
Extract from Documentation:
TheBrowse Projectspermission allows users to view issues and projects. It does not include sharing filters or managing boards.
(Source: Atlassian Support Documentation, "Manage project permissions")
Board administrator (Option C):
TheBoard administratorrole (orManage Sprintspermission for company-managed projects) allows users to manage boards, including viewing and editing them. While this would allow the team to see project boards, it grants excessive access (e.g., modifying sprints) and does not address sharing filters.
Extract from Documentation:
Board administrators can manage board settings and sprints. This role is not required to share filters or dashboards.
(Source: Atlassian Support Documentation, "Manage boards in Jira Cloud")
Administer Jira (Option D):
TheAdminister Jirapermission (Jira administrator role) grants full access to global settings, including user management, schemes, and permissions. This is far too much access for the team’s needs, which are limited to sharing filters.
Extract from Documentation:
TheAdminister Jirapermission grants access to all global settings. It is not needed for sharing filters or viewing boards.
(Source: Atlassian Support Documentation, "Manage global permissions")
Additional Notes:
The team’s inability to see project boards likely stems from lacking theView Development ToolsorManage Sprintspermission, or not being board administrators. However, the question focuses on sharing filters, soShare dashboards and filtersis the relevant permission.
The permission can be granted to the team via a group inSettings > System > Global permissions.
You want to restore a Cloud instance with another Jira Cloud backup. Which is not a valid option?
Import data
Import apps
Merge with existing Cloud users
Overwrite existing Cloud users
Import media
Restoring a Jira Cloud instance with a backup involves importing data, users, and media from thebackup file. Valid options include importing data, merging or overwriting users, and importing media. However,importing apps(Option B) is not a valid option, as apps are not included in Jira Cloud backups and must be reinstalled separately.
Explanation of the Correct Answer (Option B):
Jira Cloud backups include issues, configurations, users, and media (e.g., attachments) but do not include installed apps or their data. Restoring a backup does not involve importing apps, as apps must be reinstalled from the Atlassian Marketplace and configured separately.
Exact Extract from Documentation:
Restore Jira Cloud from a backup
A Jira Cloud backup includes:
Issues and their history.
Configurations (e.g., workflows, schemes).
Users and groups.
Media (e.g., attachments).When restoring:
Import data: Restore issues and configurations.
Merge with existing Cloud users: Add users from the backup without overwriting existing users.
Overwrite existing Cloud users: Replace existing users with those from the backup.
Import media: Restore attachments and other media.Note: Apps and their data are not included in backups. Reinstall apps from the Atlassian Marketplace after restoring.(Source: Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")
Why This Fits:Importing appsis not a valid option for restoring a Jira Cloud backup, as apps are excluded from backups, making Option B the correct answer.
Why Other Options Are Incorrect:
Import data (Option A):
Importing data is a valid option, as it restores issues, configurations, and other Jira data from the backup.
Extract from Documentation:
Import data to restore issues, projects, and configurations from a Jira Cloud backup.
(Source: Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")
Merge with existing Cloud users (Option C):
Merging users is a valid option, allowing users from the backup to be added to the existing Cloud instance without overwriting current users.
Extract from Documentation:
ChooseMerge with existing Cloud usersto add users from the backup while preserving existing user accounts.
(Source: Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")
Overwrite existing Cloud users (Option D):
Overwriting users is a valid option, replacing existing users with those from the backup.
Extract from Documentation:
ChooseOverwrite existing Cloud usersto replace current users with those from the backup.
(Source: Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")
Import media (Option E):
Importing media is a valid option, restoring attachments and other media files from the backup.
Extract from Documentation:
Import media to restore attachments and other files included in the backup.
(Source: Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")
Additional Notes:
Restoring a Jira Cloud backup requiresJira administratorororganization adminprivileges and is done viaSettings > System > Restore.
After restoring, apps must be reinstalled, and their data may need to be reimported if the app supports it.
