ALPHA team handles alerts in the ALPHA project in alpha.atlassian.net. They often view and comment on bugs in the BETA project on beta.atlassian.net. The team can link ALPHA issues to other ALPHA issues but not to BETA issues. What needs to be configured?
Correct Answer: A
The ALPHA team can view and comment on bugs in the BETA project (beta.atlassian.net) but cannot link ALPHA issues (alpha.atlassian.net) to BETA issues. This indicates a cross-site interaction issue, specifically with issue linking between two Jira Cloud sites. The solution is to configureapplication links(Option A) to enable linking between the ALPHA and BETA projects across the two sites. * Explanation of the Correct Answer (Option A): * Application linksallow Jira Cloud sites to communicate with each other, enabling features like issue linking between projects on different sites (e.g., alpha.atlassian.net and beta.atlassian.net). Without an application link between the two sites, users cannot create links from ALPHA issues to BETA issues, even if they have access to view and comment on BETA issues. Configuring an application link between the two sites will enable cross-site issue linking. * Exact Extract from Documentation: Configure application links in Jira Cloud Application links connect Jira Cloud sites or other Atlassian products, enabling features like cross-site issue linking. To create an application link: * Go toSettings > Products > Application links. * Enter the URL of the target site (e.g., beta.atlassian.net). * Follow the prompts to authenticate and configure the link.Impact: * Allows linking issues between projects on different Jira Cloud sites. * Requires permissions to view issues in the target project.Note: Requires Jira administrator permissions on both sites.(Source: Atlassian Support Documentation, "Configure application links in Jira Cloud") * Why This Fits: The inability to link ALPHA issues to BETA issues is due to the lack of an application link between alpha.atlassian.net and beta.atlassian.net. Configuring an application link resolves this, making Option A the correct answer. * Why Other Options Are Incorrect: * Global permissions (Option B): * Global permissions(e.g., Administer Jira, Browse Users) control system-wide actions within a single Jira site. They do not govern cross-site interactions like issue linking between two separate Jira Cloud sites. * Extract from Documentation: Global permissions manage actions within a single Jira site, not cross-site features like issue linking. (Source: Atlassian Support Documentation, "Manage global permissions") * Application access (Option C): * Application accessrefers to granting users access to specific Atlassian products (e.g., Jira Software, Confluence) within an organization. The ALPHA team can already view and comment on BETA issues, indicating they have access to beta.atlassian.net. Application access does not control issue linking between sites. * Extract from Documentation: Application access grants users product access but does not enable cross-site features like issuelinking. (Source: Atlassian Support Documentation, "Manage product access") * Approved domains (Option D): * Approved domainsare used to manage cross-site authentication and security for Atlassian organizations, ensuring users from approved domains can access linked sites. While this might be relevant for user authentication, the team's ability to view and comment on BETA issues suggests authentication is not the issue. The specific problem is issue linking, which requires an application link. * Extract from Documentation: Approved domains manage cross-site authentication, not specific features like issue linking. Use application links for cross-site interactions. (Source: Atlassian Support Documentation, "Manage approved domains") * Additional Notes: * Steps to configure: * On alpha.atlassian.net, go toSettings > Products > Application links. * Add a link to beta.atlassian.net and authenticate as needed. * Repeat on beta.atlassian.net to link to alpha.atlassian.net (bidirectional link). * Configuring application links requiresJira administratorprivileges on both sites. * Ensure the ALPHA team has permissions to create links (Link Issuespermission) in the ALPHA project and view issues in the BETA project. : Atlassian Support Documentation:Configure application links in Jira Cloud Atlassian Support Documentation:Manage global permissions Atlassian Support Documentation:Manage product access Atlassian Support Documentation:Manage approved domains
Question 62
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.
Correct Answer: B
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. Atlassian Support Documentation:Use smart values in Jira automation Atlassian Support Documentation:Automate your Jira Cloud instance
Question 63
Carlos describes his problem in the classic HR project * He cannot attach files to issues of Request issue type when they are in the Approved status * He can attach files to issues of Request issue type in any other status * He can attach files to every other issue issue type in every status He asks for your help in determining the root cause Select the root cause (Choose one)
Correct Answer: C
Question 64
Your Jira support project has allowed anonymous customers to create issues through an incoming mail handler for some time. In order to enhance efficiency, your project manager has inquired about the possibility of allowing anonymous users to also create issues using Jira instead of the mail handler, but without allowing further access or need of a license. Which two actions will let you meet the requirement? (Choose two.)
Correct Answer: B,E
Question 65
You inherited a mature Jira instance with hundreds of projects and associated schemes. You are trying to optimize the administration of the instance. You need to create a new project and determine which schemes to apply. Select the two best approaches. (Choose two.)
