Some issues in your project have labels and others do not.
Some tasks in your project are identified by a distinct label: daily_business. You need to prevent these issues from being displayed on the team's Scrum board
Which solution meets this requirement?
The team wants to flag issues using a category. Their requirements are:
* more than one category value can be selected on an issue
* new category values can be added by any user
* category values can be selected via a dropdown menu
* category values can be re-used across all projects
Which field meets their requirements?
Answer : D
The label field meets the team's requirements for flagging issues using a category. Labels are a type of custom field that allow users to add one or more descriptive tags to issues. Users can add new labels on the fly, and select existing labels from a dropdown menu. Labels can be re-used across all projects, and can be searched and filtered easily. A text field does not allow multiple values or a dropdown menu. A component does not allow multiple values or adding new values by any user. A user picker does not allow multiple values or adding new values by any user. Checkboxes do not allow adding new values by any user.Reference:[Adding, removing and searching for labels], [Managing Jira Projects Data Center and Server: Certification Bundle]
You want to create a new Scrum board with the following requirements:
* Show all issue types from project BERT but do not show sub-tasks in the backlog
* Show only epics from project ERNIE
* Do not show issues from any other projects
Which board filler query meets these requirements?
The ''Open issues filter of your project shows bugs, along with epics and stones.
You then view the project's Scrum board where you only see epics and stories but not bugs.
Which configuration is responsible for this behavior?
Answer : A
Your team failed to meet their last sprint commitment and you want to investigate further. You need an agile report that:
* shows you a list of the incomplete issues in the sprint
* allows you to quickly view that list in the Issue Navigator
Which report meets this need?
Your team uses a custom field of type Labels to track keywords associated with incoming requests. Issues can have multiple keywords, and new keywords can be added at any time. They want to see keywords displayed prominently when viewing all cards on a board. Which configuration meets this need?
Answer : A
The best configuration to meet the team's need of displaying keywords prominently when viewing all cards on a board is card layout. Card layout allows you to customize what fields are shown on each card on a board, and you can choose to show any custom field of type Labels on the cards. Swimlanes are used to group issues into horizontal lanes based on certain criteria, such as assignee, priority, or query, but they do not show labels on each card. Card colours are used to highlight issues based on certain attributes, such as issue type, priority, or query, but they do not show labels on each card either. Issue detail view is used to show more information about an issue when you select it on a board, but it does not affect how cards are displayed on the board. Therefore, the correct answer is A.Reference: [Configuring card layout], [Configuring swimlanes], [Configuring card colours], [Using boards]
You need to assign team members to view code commits in the DEV project. An excerpt of the DEV permission scheme is shown.
Which two project roles must they be granted? (Choose two.)
Answer : B, C
Two project roles that must be granted to view code commits in the DEV project are:
Developers
Administrators
According to the image you sent, the View Development Tools permission determines which users can see development information from tools such as Bitbucket, GitHub, FishEye, and Crucible. This permission is granted to the Project role (Developers) and the Project role (Administrators) in the DEV permission scheme. Therefore, users who are assigned to these roles will be able to view code commits in the DEV project.
The other options are not correct because:
Users do not have the View Development Tools permission in the DEV permission scheme, so they cannot see code commits in the DEV project.
Sprinters do not have the View Development Tools permission in the DEV permission scheme, so they cannot see code commits in the DEV project.
Managers do not have the View Development Tools permission in the DEV permission scheme, so they cannot see code commits in the DEV project.