Prueba ACP

Which three factors should you consider when deciding between Jira Cloud and Jira Server? (Choose three.). the ability to integrate Jira with a cloud-based source repository (e.g. Bitbucket). the amount of time required for system administration. the availability of a REST API. the commercial apps you would like to use. the ability to integrate with an external user directory (e.g. company LDAP directory). the number of workflows you will require.

You want to introduce Jira to your small non-profit organization. Since you are unsure of the optimal deployment option you have gathered some requirements: ✑ You need to manage a team of up to 15 employees. ✑ You need to be able to track a backlog of staff action items. ✑ You want to easily visualize the progress of ongoing work. The solution must require minimal administration since your organization only has a part-time IT volunteer. What solution is most appropriate for your organization?. Jira Service Desk Cloud. Jira Software Data Center. Jira Service Desk Data Center. Jira Core Server.

The marketing team has asked you to embed the trigger tab of an issue collector on several internal web pages and change its size, color, and text. They also want the ability to track which webpage finally generated the underlying feedback issue. You are not familiar with advanced issue collector configuration. Which type of developer should you contact for assistance?. Velocity. SQL. Groovy. JavaScript. Phyton.

Your Jira has 25,000 active users across the globe using 100 projects with over a million issues. Another administrator has made a change to a field configuration scheme and you now need to re-index Jira. What would be the impact of rebuilding the index in the foreground?. Issues will take longer to display during the re-index. Database backups cannot be run until the re-indexing is complete. The configuration change will not be applied until re-indexing is complete. Searches using the field may show erroneous results. All users will be locked out of Jira until re-indexing completes.

The configuration details of an SMTP Mail Server of a Jira instance are shown below. The configuration hasn't been changed in the last 24 months. Email volume has increased and the Timeout is too low. The Jira license has expired. The database and/or server disk is full. The SMTP password has expired. The user Jira has no valid Jira license.

Jan asked you to create a new Select List custom field called Department for his project MCAS. You created the field in the morning. In the afternoon, Jan notes that his Jira dashboard is not showing the field correctly. He asks to help him troubleshoot. View the Exhibit to see Jan's entire dashboard. ✑ The first gadget shows 26 issues in the project by Status. ✑ The second gadget shows that there are three issues that have the new Department field set. The last gadget shows "No Data Available". The filter query for that gadget is "project=MCAS and Department is empty.". You created the field Department but did not re-index the MCAS project. The JQL query for the filter is not valid. Jan does not have the proper Browse permissions. There is issue security on the issues. The field context on the Department field was not set to allow empty values. The field is marked Optional in the Field Configuration.

You are moving a workflow from your staging Jira instance to production. On importing the workflow, Jira notifies you that the post-functions will not be imported. Staging Jira is on version 6.4 and production Jira is on version 6.3. Why did this happen?. The apps installed on staging are not the same as on production. The production and staging instances are using different versions of Jira. Custom post-functions are not included in workflow export. You exported the workflow as XML instead of JWB.

You have planned, tested, and performed a Jira upgrade. The upgrade appeared to be a success; however, after several hours of use, your users are reporting significant problems and you decide to roll back. Which two effects do you expect to see after the rollback? (Choose two.). The color scheme will be set back to default to indicate there was a rollback. Emails will automatically be sent out to tell people about the rollback. Jira will need to be reconnected to other systems it was integrated with. Jira will go back to the same schemes as before the upgrade. New issues entered between upgrade and rollback will be lost.

The Active Directory administrators have just started the process of copying all the users from the old Company B directory to Company A directory. During this process, the group membership is being changed to allow for more fine-grained security control. A large number of migrated users complain that they do not have the correct new group memberships. Which configuration change should you perform?. Enable the Crowd user directory. Synchronize the Company A directory. Reorder the directories so Company A is before Company B. Disable the Company A directory. Reorder the directories so the Jira Internal Directory is listed first. Disable the Company B directory.

After a recent upgrade to your Jira system, one of the apps your organization depends on is not working reliably. Which two methods can you use to debug and resolve this issue? (Choose two.). Ask the System Administrator for catalina.out logs and inspect for stack traces. Ask the System Administrator to enable the SQL log. Ask the System Administrator to set package com.atlassian to Trace logging level. Ask the System Administrator to add the app to the logger. Ask the System Administrator to set the logging level to FATAL on all package names, Under Logging & Profiling.

A team is complaining that their Jira project is slow to use. You are able to replicate the slow behavior by viewing and trying to edit one of their issues. Which logging option will help you or a system administrator to diagnose the problem?. Use the Log Analyzer to get more information about the issue view process. Configure Jira to record and log the JavaScript execution from the browser console. Set the logging to DEBUG level on all packages causing activity for that issue. Enable profiling globally, so the logs can be inspected for anomalies when viewing the issue.

Max wants you to change the way the system fields Created or Updated are being displayed when viewing an issue. How can this be achieved?. Adjust the Day Format in the Jira look and Feel configuration. Adjust the jira.date.time.picker.java.format in the advanced settings configuration. Adjust the jira.date.picker.java.format in the advanced settings configuration. Adjust the Complete Date/Time Format in the Jira Look and Feel configuration. Adjust the language and time zone preferences in Max's user profile.

Three team members have left the company and their issues need to be re-assigned to various -users. All of their issues are in the Marketing project which uses the Default Notification Scheme. The scheme has never been updated. How do you inform the new assignees about their re-assigned issues?. Add an announcement banner to the marketing project to inform team members. Perform a single bulk operation to mention all new assignees in a comment. Add an announcement banner to each new assignee's dashboard. Perform bulk operations to re-assign the issues and notify the new assignees. Use the Send email feature to inform the individual new assignees.

Which time tracking configuration can be controlled on a global basis for all projects in Jira?. which users or groups have the ability to log work on issues. whether time tracking fields are available on standard versus sub-task issue types. the default time unit on estimates when users don't explicitly specify one. which users have the ability to edit or delete their own or other users' worklogs. whether Original Estimate is required when creating issues.

A project manager wants to stay aware of the support requests that are being raised in his project. He wants to know if: ✑ the team is able to handle the number of issues that are being raised in the project ✑ there are team members who work on more than 2 issues at any given time ✑ there are sets of issues that need significantly more time to resolve when compared to others over time Which three gadgets will show him the information he needs? (Choose three.). Activity Stream. Created vs. Resolved Chart. Two Dimensional Filter Statistics. Resolution Time. Labels.

Managers want to ensure that every issue in Jira always has an assignee. Which change will definitely meet this requirement?. Update post functions to set the assignee appropriately at each workflow transition. Set Default Assignee to Project Lead in every project. Use components for automatic assignment in every project. Make the assignee required on workflow transition screens. Make the assignee required through field configurations. Set the global option "Allow unassigned issues" to OFF.

Your company will migrate to Jira. You plan to import with a CSV file. Which fields are required as CSV columns for your import?. Project. Project, Summary. Summary. Project, Issue Type. Summary, Issue Type.

Sundar's development projects are falling behind. He wants to write a JQL query to find issues that meet all three of these criteria: 1. He is the project lead of the project or the project is DEV. 2. fixVersion had been set to 4.3 at some point but was later removed. 3. Issues were created in the first 15 days of this month. The Exhibit shows the JQL query he created. Which statement about Sundar's query is true?. The query will not return the right set of issues because the parentheses are wrong. The query will not return the right set of issues because lines 2 and 3 are wrong. The query will return the right set of issues, but it is inefficient. The query is well written and will return the right set of issues. The query is valid, but it will not run without a Jira Marketplace app. The query will not return the right set of issues because line 2 only is wrong.

A team complains that many of their issues are in the Closed status, but do not have a resolution set, which causes problems with reporting. The project uses a single workflow. You want to set the resolution to Done on all existing issues in the Closed status. Which combination of workflow elements and a bulk operation will achieve this?. ✑ A temporary transition and a trigger ✑ An Edit Issues bulk operation. ✑ A temporary transition and a post function ✑ A Transition Issues bulk operation. A screen and the Resolution field ✑ A Move Issues bulk operation. ✑ A screen and a custom field ✑ An Edit Issues bulk operation. ✑ A temporary transition and a screen ✑ An Edit Issues bulk operation.

Tom has asked you why the numbers returned by his searches are not right. He shows you three JQL queries: How can you fix this?. Change the query to project = "Cake Baking" and fixVersion ~ 1.1.0. Change the query to project = "Cake Baking" and ( fixVersion is empty or fixVersion != 1.1.0 ). Rename the versions so they do not contain periods. Identify the missing issues and change the permissions so that everyone can see them. Change the query to project = "Cake Baking" and fixVersion not in (1.1.0).

One of the HR managers created a filter and shared the subscription with members of the hr-managers group. The filter contains the following valid JQL query: Manager = currentUser() AND Manager in membersOf("hr-managers") Which issues will be included in the subscription?. Only issues where the user who created the filter is listed in the Manager field. Only issues where the group hr-managers is listed in the Manager field. Only issues where the recipient of the email is listed in the Manager field. All issues where the user listed in the Manager field is a member of the hr-managers group. All issues that are assigned to any member of the hr-managers group.

Your marketing company wants to evaluate Jira and purchased a 10-user license. A frequently changing group of key stakeholders "" both internal employees and external customers "" will participate in the evaluation. If the evaluation is successful the company wants all 50 employees to start working with the tool. You have to manage the frequently changing group of stakeholders and need to make sure only the intended users participate in the evaluation. How should you meet these requirements?. Create and manage the users for stakeholders manually in the internal directory. Connect Jira to your internal LDAP directory and whitelist the IPs of stakeholders. Enable public signup and CAPTCHA but limit account creation to stakeholders. Disable public signup and grant all project permissions to Group Anyone.

Some of your project owners would like to make their projects publicly accessible over the Internet. These projects will not require login. You could support this by allowing read-only anonymous access to the projects. Which two additional factors should you take into consideration when setting this up? (Choose two.). Anonymous users could see other users' names. Anonymous users could export all issues from Jira. Licensed users might accidentally comment anonymously rather than logging in first. Internet search engines could index data. Anonymous users could find a full list of all your projects. Spam bots could add comments.

You have been asked to take on the administration of a second Jira installation in your company. You were given the following information about user accounts: ✑ The company standard is to use Active Directory (AD) to provide user accounts. ✑ There are several Active Directory systems in use by different business units. ✑ The second Jira is not to be merged with your main Jira. ✑ The main Jira system is connected to Active Directory for user accounts. ✑ The second Jira is using internal user accounts, not Active Directory. ✑ People using the second Jira are using the same login ID as they would use in Active Directory. ✑ Your company would like to use Single Sign-on (SSO) but has not yet implemented it for either Jira system. Which authentication method should you recommend?. Change the new Jira to use your main Jira's directory services, as that is already reading your Active Directory services. Set up a Crowd server to get the user lists from all internal directories and AD, and use AD directly for the password checking. Set up a Crowd server to pull in all the AD services, and plan to migrate internal users. Change the new Jira to link directly to the required AD servers.

Beehive Bank wants to implement Jira with the following requirements: ✑ Enforce the strictest possible security measures for user logins. ✑ Allow external users to create their own user logins. ✑ Use the Jira Internal Directory. Which two login security options can you offer them? (Choose two.). Set Login Mode to Secure. Require character variety for the user name. Require that a password is not too similar to another user's password. Require a certain length for passwords. Require that a password is not too similar to the user name or email address.

You have two issue types in your HR project: Hire and Fire. Which two requirements can be met through changes only to field configurations? (Choose two.). For the Fire issue type, the Description field should have a default value of "Termination". For both issue types, the Employee Name custom field must be required upon creation and must never be blank. For the Hire issue type, the field description for the Due Date field should read "First day of work". For both issue types, the Resolution should be set once the issues are being resolved. For both issue types, the Assignee field should be hidden when creating but not when viewing an issue. For the Fire issue type, the default value for the Priority field should be Blocker.

Your HR project has two issue types: ✑ Join ✑ Leave Both issue types share a field configuration, screens and the workflow. You currently use the Due Date system field to indicate when someone actually joins or leaves. New HR staff members complain that using the Due Date field is not very intuitive. How can you help your HR team?. ✑ Create individual Join Date and Leave Date custom fields to replace the Due Date field. ✑ Create separate screens for each issue operation and issue type. ✑ Delete the Due Date field. ✑ Rename the Due Date field to Join Date and create a separate Leave Date custom field. ✑ Create new screens for the Leave issue type and replace the Due Date field with the newly created field. ✑ Migrate existing field values to the new Leave Date field. ✑ Create individual field contexts for each issue type. ✑ Label the Due Date field as Join Date and Leave Date in their respective contexts. ✑ Associate each context with its matching issue type. Create individual Join Date and Leave Date custom fields to replace the Due Date field. ✑ Appropriately migrate existing data from the Due Date field to the new custom fields. ✑ Remove the Due Date field from all project screens.

You install a new Jira instance using only the default configurations. A team approaches you to set up a project with the following specifications: ✑ There are four standard issue types and three sub-task issue types. ✑ The first sub-task will need a new screen for the Edit operation. ✑ The second sub-task will need new screens for both the Create and Edit operations. ✑ Everything else should use the default configurations. How many new Screen Schemes do you need to create?. 7. 4. 1. 3. 2.

You set up a new project for a team. Soon afterward, users report that a field is missing from one of their screens. You check the screen configuration in the administration panel and you see that the field should be present. Why can't the users see the field?. The changes to the screen were not published. The issue operation wasn't mapped to a screen. The field context does not include the project and/or issue type. The users don't have permission to view that field.

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?. Reorder the statues on the Status administration page. Change the Sort Direction option in the gadget to Ascending. Change the category of the statuses. Add numbers to the status names to allow them to be sorted in numerical order. Change the gadget Sort By field to Total.

A team of technical writers works in the WRITE project. The project uses a single, shared workflow. To better match the team's way of working they request a workflow change: ✑ The initial status of their project's workflow should be changed from Open to Awaiting Inspiration. You navigate to the Workflows section of the administration, update the Name of the status in the workflow designer and publish your change. What are two implications of this change? (Choose two.). The workflow scheme for the WRITE project will need to be published before the change takes effect. Awaiting Inspiration will be created as a new Status in Jira. Transitions to the Awaiting Inspiration status will fail until the post functions for those transitions are updated. Filters and Gadgets that referred to the Open status by name will be broken. The Open Status will be changed to Awaiting Inspiration in all workflows using that status.

You are tidying up a Jira project and find that the following two issue types are being used. ✑ Task ✑ Assignment They seem very similar. If both are not needed, you could convert all existing Assignment issues in the project into Task issues and remove the Assignment issue type from the project. Which project configurations would you check to see if it is necessary to keep the two as separate issue types instead? (Choose three.). Issue Security Levels. Field Configurations. Components. Permissions. Workflows. Field Contexts.

A team requests updates to the behavior of some fields in the project. The project uses three issue types: Problem, Incident, and Change. The desired configuration is shown below: Which configuration update will meet the requirements?. Configure individual screens for each issue type and update the priority scheme. Configure individual field configuration for each custom field and update the priority scheme. Create unique field contexts for each issue type for the desired fields. Configure individual field configurations for each issue type. Configure individual field contexts for each custom field and update the priority scheme. Configure individual screens for any combination of issue operation and issue type.

There is clearly an hour's difference between the Original and Remaining estimates. Identify two possible reasons Logged Time is showing as Not Specified. (Choose two.). Time tracking was not enabled when the work was logged. The remaining estimate was adjusted without logging any effort. The hour's work was logged via a REST call by the user. The work log would have exceeded the project's time allowance, so it cannot be counted. The original estimate was increased. You do not have view permission to see the logged work.

In your organization, a cobbler leads a Jira project with two issue types: ✑ Shoe Order ✑ Repair The cobbler has given you the following requirements: 1. All screens should use the Summary, Description, Due Date, and Components fields. 2. Both issue types need to use a new custom field called Shoe Type on all screens. 3. The Priority field should appear on all screens for Repair issues. 4. Users should not be able to set the Priority for Shoe Orders during creation, but the Priority field still needs to be editable and viewable after creation. Identify the minimum number of screens and screen schemes that will meet the requirements. two screens and one screen scheme. one screen and one screen scheme. six screens and one screen scheme. six screens and two screen schemes. three screens and one screen scheme. two screens and two screen schemes.

One of your teams has noticed a spelling mistake in the name of an issue type. What should you do before correcting the name of the issue type?. Warn users that dashboard gadgets that refer to the issue type in their configuration will need to be updated with the corrected name. Warn users that saved filters using the issue type will not be able to find the issue type after the change. Update the issue type schemes to refer to the new name. Update the workflow schemes for the issue type to use the new name.

A project lead wants to conduct historical trend analysis, but she is worried that older issues are being updated in a way that inhibits their comparison. She wants to take a snapshot of the data in her project at regular intervals so she can compare different periods. Which tool will help meet this need?. Backup Jira data. Project Export. JQL Results Snapshot. Issue Filter Export to CSV.

A project has hundreds of old completed issues which are cluttering up the reports, searches, and dashboards. The project administrator has the following requirements: 1. He wants to hide the old issues. 2. He wants to unhide issues, if needed. 3. He wants to control whether he himself sees the hidden issues, so they do not clutter his own daily work. Which three configurations, when combined, will meet these requirements? (Choose three.). security level. project permission. workflow condition. project role. global permission. group.

You are setting up a new Jira instance and three new projects with shared configuration. There are many managers at the company and you need to structure their permissions accordingly. Which requirement can only be met with a Managers project role?. Different managers need to delete issues in different projects. Only some managers must be selectable from a custom field, depending on the project. Managers need to be able to create shared dashboards. Only managers who are project leads can see the restricted security level in their own projects. Any manager should be able to view the development tools in any project.

Contractors will begin using your Jira instance. You receive the following requirements for them: How should you manage global permissions for the contractors user group?. Grant them the Browse Users permission. Grant them the Bulk Change permission. Grant them the Jira System Administrators permission. Grant them the Manage Group Filter Subscriptions permission. Grant them the Create Shared Objects permission.

A medical clinic has decided to use Jira. Their project will allow patients to file medical complaints. The requirements for the project are as follows: ✑ Members of the group (jira-patients) must be able to see only their own complaints. ✑ Members of the group (medical-board) must be able to see all complaints. Based only on these two requirements, which two configurations used together will satisfy them? (Choose two.). Implement an issue security scheme with three levels: (#1) Group (jira-patients), (#2) Reporter, and (#3) Group (medical-board). Implement an issue security scheme with two levels: (#1) Reporter and (#2) Group (medical-board). In the permission scheme, add Reporter and Group (anonymous) to Browse Projects and Create Issues. In the permission scheme, add Group (jira-patients) and Group (medical-board) to Browse Projects and Create Issues permissions. Implement an issue security scheme with one level: Reporter and Group (medical-board).

Many projects share the same permission scheme and workflow scheme. The requirements in those projects are: ✑ Only Translators should be able to use the Translation workflow transition. ✑ The same team of Translators work across all the projects. How should Translators be configured to meet these requirements?. As a group. As single users. As a Group custom field. As a User custom field. As a project role.

Martin has Create Attachments permission in a software project, but he cannot attach anything to issues in Approved status. What is the problem?. There is a workflow step property configured. He is not a member of a security level. There is a workflow condition configured. The Attachment field is missing from the screen for that issue type. He does not have the correct project permission.

The OPS team will start using Jira to track and approve Change Requests in the OPS project. They have these workflow requirements: ✑ Requests can be approved by two individuals only. ✑ The approvers will change weekly. Jira is connected to your corporate LDAP with Read-Only permissions. What is the best way to structure permissions for the OPS project to support these workflow requirements?. Create the group it-approvers in the Jira Internal Directory and have the approvers maintain it. Create a new project role for approvers and have the Project Role (Administrators) maintain it. Request the group it-approvers to be created in the corporate LDAP directory and add it to the Approve Issues permission for the project. Request the group it-approvers to be created in the corporate LDAP directory and have the Project Role (Administrators) maintain it in Jira. Add individual names to Project Role (Administrators) and add this role to the Approve Issues permission for the project.

Your business owners have told you to use roles as much as possible in Jira because it allows them to do things that groups cannot do. When considering this, you need to be aware of those actions in Jira that require the use of groups rather than roles. Identify two actions in Jira that require the use of groups. (Choose two.). allowing users to use transitions in all the workflows. granting Project Administration rights. granting permissions to teams coming from Active Directory. defining Issue Security levels. granting system administrative rights. controlling who can perform Bulk Change in a project.

Jon is a new Jira user. He reports that adding comments to Jira isn't working as expected. When he attempts to @mention a user, no list of available users is provided. Because he does not know everyone's username, he is unable to target comments to specific users. What is the cause of this problem?. Jon does not have the Browse Users global permission. Jon does not have the View Users project permission. Jon does not have the correct field security permission for the Comment field. The field configuration for the Comment field is not set to Autocomplete Renderer.

You needed to replace the legacy Jira group all-staff-europe with a newly created all-staff-global group. You created the new group and you migrated all users to the new group. Then you deleted the legacy group. Which four problems might users report after the change? (Choose four.). Filter subscriptions send out errors instead of issues statistics. Workflow transitions are hidden from certain users. Users are not able to perform bulk change operations. Users are not able to log in to Jira anymore. Comments that were restricted to the legacy group are lost. Filter results return an incorrect number of issues.

Critical production bugs in a Jira Software project are hidden with an issue security scheme that has a single security level. Only project administrators are listed in the security level and granted the Set Issue Security permission. A new requirement states that a few other Jira Core users, who have Browse Projects permission, should be able to see the hidden issues. These users will vary per issue and be selected from across various groups. What needs to be added to the security level?. Application access. User custom field value. Group custom field value. Project role. Single Users. Group.

You have just deployed a new Support Workflow and Support Notification Scheme. Manager Maria should be receiving notifications when users click the Escalate workflow transition, but she is not. Identify two possible reasons Maria is not receiving the notifications. (Choose two.). Maria is not listed in the right custom event of the Support Notification Scheme. The Escalate workflow transition is firing the wrong event. The right custom event has been deleted from the Support Notification Scheme. Maria is not listed in the Issue Escalated (System) event of the Support Notification Scheme. The Escalate workflow transition is firing the right event, but the event is marked Inactive. The Escalate workflow transition is firing the right event but uses the wrong email template.

Your business users want to know more about what is happening with the issues raised by their business unit. They gave you a list of situations in which they want to get emails, so you know which parts of the shared notification scheme they want to be added to. You consult with the project owner. He doesn't want any changes to the emails that go to developers and testers. The project owner approves of the business users getting the emails, but he would like to retain control of who gets emails for his project. How can you satisfy these requests?. Place the business users in a group and add that group to the events in the notification scheme. Modify the events in the workflow so they send the emails to the business users. Create a role for business users and add that role to the events in the notification scheme. Add the business users as Watchers on the issues.

The HR team approaches you with new requirements they want you to implement: ✑ Allow users to send requests into Jira by emailing "HR@yourcompany.com." ✑ Have those emails automatically turned into "Holiday Requests" in the HR project. You have already set up an Incoming Mail Server and a mail handler to "Create a new issue or add a comment to an existing issue." Which three additional options can you set with this mail configuration? (Choose three.). Create new Jira users based on the From address. Set Assignee and Watchers. Set default Reporter. Set a custom field. Set Environment.

Inspect your current Incoming Mail Handler configuration: Identify one reason why the current configuration is not fetching emails as planned. The blank space in the Incoming Mail Handler name will cause internal errors. The syntax of the specified Folder Name is invalid and should be corrected to "˜/spam'. The syntax of the specified Folder Name is invalid and should be corrected to "˜/spam'. The external mail service is not able to write the messages to the specified folder.

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.). Create a custom project template that uses the most common shared schemes. Use the Scheme Helper admin tool to see which combinations of schemes are compatible. Use one of the project templates other than Jira Default Schemes. Attempt to generalize existing schemes with project roles and share those. Evaluate existing shared schemes based on common project category or other criteria. Create a project using the Jira Default Schemes and then create new schemes to avoid sharing conflicts.

You are designing a complex new workflow. Two of the requirements are listed below: 1. Any user should be able to trigger the Put On Hold transition from any status in the workflow. 2. Only users with the Close Issues permission should be able to Close the issue at any point in the flow. Based only on these requirements, which two workflow elements should you use? (Choose two.). Global Transitions. Conditions. Triggers. Validators. Common Transitions.

A project is using the Approval workflow shown. The project lead has communicated the following change requests: ✑ It should be possible to transition issues into the Awaiting Approval status from any other status apart from the Approved status. ✑ Different transition screens will be needed for each transition into the Awaiting Approval status. How do you configure the workflow to satisfy these requirements?. ✑ Create a global transition to the Awaiting Approval status. ✑ Create multiple appropriate transition screens and associate it with the global transition. ✑ Reuse the Request approval transition between the Open and Awaiting Approval status. ✑ Create an appropriate transition screen and associate it with the transition. ✑ Create a transition from the Open to the Awaiting Approval status. ✑ Create appropriate transition screens and associate them with the individual transitions into the Awaiting Approval status. ✑ Create a global transition to the Awaiting Approval status. ✑ Create an appropriate transition screen and associate it with the global transition. ✑ Create a transition from the Open to the Awaiting Approval status. ✑ Reuse the existing transition screen from the Request approval transition.

You receive workflow configuration requirements for issues in the Closed status. They are as follows: ✑ Users must NOT be able to edit issues in this status. ✑ Jira administrators must be able to edit issues in this status. ✑ Only users in the release-managers group should see the transition to the Re-opened status Which combination of two workflow configuration items should you use to meet these requirements? (Choose two.). Properties. Post functions. Conditions. Validators. Triggers.

You need to make the following changes to an existing workflow: 1. A transition should only be available if code has been committed against the issue. 2. Only users in a specific project role can see a transition 3. Issues must not be commented on in a specific status. 4. The resolution should be set automatically. 5. A transition should send out a specific notification email. Which workflow elements will you use to implement the desired changes?. 1 condition, 1 validator, 2 post functions, 1 property. 2 conditions, 2 validators, 1 property. 1 condition, 1 validator, 1 post function, 2 properties. 2 validators, 2 post functions, 1 property. 2 conditions, 2 post functions, 1 property.

A user says she can see the Ready for Testing transition but cannot successfully execute it. Why can't the user execute this transition?. The status property of Code Review prevents the Developer role from executing the transition. A Condition on the transition requires the user to be in the Developer role. A Validator on the workflow transition requires the user to be in the Developer role. The status property of In Progress prevents the Developer role from executing the transition.

You have a project with several issue types, associated unique workflows, and a number of components. The decision has been made to have all new issues assigned automatically. To that end, you've set default assignee(s) for the project lead, component leads, and removed the Assignee field from the screens associated with the Create Issue operation. One of the issue types is still being created without an Assignee. What is the most likely cause of the problem?. The issue type's field configuration for Component/s is not set to Required. The default assignee for the issues' component is still set to Unassigned. The post function Assign to Lead Developer is missing in the create transition. Users creating this issue type do not have the Assign Issue permission. The assignee is being set to Unassigned in the first post-function of the create transition.

Your project has three issue types that share a common workflow. Which reason would make you recommend the implementation of separate workflows for each issue type?. The issue types need different sets of priorities. Each issue type uses a different issue security level. Different project roles are working on the issue types. One of the issue types needs a new status. The issue types need different sets of resolutions.

Your administration project is configured as follows: ✑ there are three issue types that all share a single workflow ✑ all project users are members of the Project Users project role ✑ all members of the Administrators project role have the Set Issue Security permission ✑ project administrators are the only users who can create issues You are tasked with replacing the Project Users project role with three distinct team project roles, each solely responsible for one of the issue types. Which additional requirement can be met by individual workflows per issue type?. The system field Component/s needs to be required when creating two out of the three existing issue types. Each issue type needs a dedicated set of individual project components. The reporter and current assignee of each issue should always have access to view it. Only members of the dedicated teams should be able to view and work on the issues they are responsible for. Individual notifications should be sent out depending on the selected issue type.

You are prompted to perform a re-index after you have made configuration changes to a very large Jira instance. Which reason would justify re-indexing only a project instead of a full re-index of the instance?. Workflow changes were limited to the project's unique workflow. Time tracking was modified for the project. Only custom fields used by the project were modified. Only project users would be affected by the re-index.

Your project is configured as follows: ✑ several issue types, components and versions ✑ a single, simple unique workflow "" OPEN --> IN PROGRESS --> DONE ✑ Fix Version(s) can be set on the transition to IN PROGRESS ✑ Component(s) are required and new issues are automatically assigned to component leads ✑ all component leads are members of the Administrators project role Now you have to implement the following requirements: ✑ an affected version needs to be added to the issue upon creation ✑ only component leads can choose or add a fix version when the issue is transitioned to IN PROGRESS What two configurations are prerequisites to meet the requirements? (Choose two.). Ensure Affects Versions/s is required in the used field configurations and on the correct screen. Add a condition limiting execution to the Administrators role to the IN PROGRESS transition and require Fix Version/s to be set. Ensure Component/s, Affects Versions/s, and Fix Version/s are required in the used field configurations. Ensure that only members of the Administrators project role have Resolve Issues permission. Add a condition limiting execution to the IN PROGRESS transition to the current assignee.

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.). Create an issue security scheme with a default level allowing only licensed Jira users to access issues. Ensure that the Jira mode in the general configuration has been set to Public. Add Group Anyone to the Browse Projects permission in the project's permission scheme. Add Group Anyone to the Create Issues permission in the project's permission scheme. Ensure that the Reporter is not required in the project's field configuration scheme.

Your organization has a Jira project for managing work on a software development project. As the team has grown, two groups have formed within it, working on different tasks. To help bring more focus to the work being conducted, the team has requested a second Jira project to split the team's work into two. Which set of schemes can likely be shared between the two projects?. Custom Field and Issue Security. Resolution and Notification. Workflow and Custom Field. Issue Type and Sub-task. Notification and Workflow.

The Release Manager is having problems caused by inconsistent naming of versions across projects. He would like to use a more consistent naming convention. The developers do not know the naming convention, and are happy to let the Release Manager rename versions when they get the names wrong. The projects all use the Default Permission Scheme. Which action would allow the Release Manager to update the versions in the projects?. Change the Manage Versions permission in the permission scheme. Change the workflow to allow the Release Manager to update versions. Add the Release Manager to the Administrators project role. Add the Release Manager to the developer role.

One of your teams is maintaining and updating an application that has grown into three distinct modules. The modules are on different release cycles. The team is struggling to track the versions of the modules, because they have similar numbering schemes. Which action would you recommend?. Define an issue type for each module. Create a new Version field for each module. Split the modules into separate components. Split the project into several projects, one for each module.

One of your project owners is struggling with reporting and sorting issues in her project. Currently, the classification of the issues is no more useful than a list of things that need to be done. The project owners would like to establish the following: ✑ more classification of issues, so issues can belong to several classes ✑ the ability to edit classes ✑ a way to link a class to an owner How would you help this project owner improve issue reporting and sorting?. Add a custom field of type Select List (multiple choices) for class, linked to a class-owner field. Ensure the component field is available in the project and demonstrate how to use it. Add a new labels field for the project, with labels containing the owner names. Add a custom field of type Select List (cascading) with classes in the first tier and owners in the second tier. Add a custom field of type Select List (multiple choices) for class, naming an owner in the options.

Identify three project settings that will immediately improve the viewing of projects on this page and the search results in Issue Navigator. (Choose three.). Add URLs for search engine optimization. Add project tags. Add client logos as project avatars. Create project categories by client. Add project descriptions. Set the project lead to the appropriate Project Administrator.

Which two requirements would require creating a new project? (Choose two.). Change requests will not use versions. Change requests will have different component leads. Change requests will have a different workflow. Change requests will notify different people for all system events. Change requests will require the Due Date field to be populated.

Your marketing group is using Jira to track media print advertisements. They would like to track TV and radio commercials as well. The same team handles all three formats, but each format requires a unique workflow. The team would like to keep everything on the same dashboard, and they will also be using the same permissions, notifications and screens. Without using third-party apps, how should you configure Jira to meet these requirements?. Clone the existing project and key for TV and Radio. Copy the existing permissions and notification schemes, and associate them with new projects for TV and Radio. Create a sub-component hierarchy. Create two new projects for TV and Radio. Add TV and Radio into the existing project as components. Use issue types of Print, Radio and TV in the existing project.

Which statement is true about changing a project's key?. Users have to update issue filters referencing the old project key. Unshared project schemes will be automatically renamed to reflect the new project key. External links to issues in that project need to be updated to match the new project key. The old project key can be reused for a new project. Internal Jira links referencing an old key will continue to work.