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?
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]
Which statement is definitely true about priorities in Jira?
Jira administrators can create and update global priorities, which are the default set of priorities available in each project. Project administrators cannot re-order, create, or update priorities in their projects, unless they have Jira administrator access. The same set of priorities is not always available in each project, as Jira administrators can configure priority schemes to assign different priorities to different projects.Reference:[Configuring priorities], [Managing Jira Projects Data Center and Server: Certification Bundle]
Jon notices that an issue was created incorrectly in project
Jon needs Move Issues and Create Issues permissions to move an issue from project A to project B. Move Issues permission allows him to initiate the move operation, while Create Issues permission allows him to create the issue in the destination project. Transition Issues permission is not relevant for moving issues, as it only affects workflow transitions. Administer Projects permission is not required for moving issues, unless the issue type or workflow needs to be changed during the move. Assign Issues permission is not required for moving issues, unless the assignee needs to be changed during the move.Reference:[Moving an issue], [Managing Jira Projects Data Center and Server: Certification Bundle]
All stories in your project are linked to epics within the same project. Using a bulk operation, you moved some stories to another project. What happens to the epics?
Epics are moved automatically but epic links are lost when stories are moved to another project using a bulk operation. This is because epics are a type of issue, and issues can be moved across projects. However, epic links are a type of issue link, and issue links cannot be moved across projects. Therefore, the stories will lose their epic links after the move, and the epics will remain in the original project.Reference:[Moving multiple issues], [Managing Jira Projects Data Center and Server: Certification Bundle]
A Scrum project has the following five configured versions:
How many of them will be available in the versions panel of the project backlog?
Three versions will be available in the versions panel of the project backlog: epsilon, delta, and gamma. These are the three unreleased versions in the project, as shown in the image. The versions panel only shows unreleased versions, as they are used to plan and track the progress of upcoming releases. Released and archived versions are not shown in the versions panel, as they are considered completed and no longer relevant for planning purposes.Reference:[Working with versions], [Managing Jira Projects Data Center and Server: Certification Bundle]
Full Exam Access, Actual Exam Questions, Validated Answers, Anytime Anywhere, No Download Limits, No Practice Limits
Get All 75 Questions & Answers