Your team is using a Scrum board and has many issues planned for future sprints. You need to configure a secondary board that· excludes those planned issues from the board but not from the reports · hides issues in real time when users select multiple conditions Which two board configurations satisfy the requirements? (Choose two.)
Answer(s): B,E
To exclude the planned issues from the board but not from the reports, you need to use a board sub- filter. A board sub-filter is an additional JQL query that is applied to the board filter to further refine the issues displayed on the board. The sub-filter does not affect the reports, which are based on the board filter only. To hide issues in real time when users select multiple conditions, you need to use quick filters. Quick filters are buttons that allow users to dynamically change the view of the board by applying one or more JQL queries. Users can select or deselect quick filters to show or hide issues that match the criteria.
Configuring filters, Configuring quick filters
Quang can transition issues from Resolved to Done using the workflow button on issues in his project. However, he cannot drag then from Resolved to Done on the project's Kanban board Identify a possible reason why.
Answer(s): C
If Quang can transition issues from Resolved to Done using the workflow button on issues in his project, but cannot drag them from Resolved to Done on the project's Kanban board, a possible reason is that the statuses are mapped to the same column. The columns on a Kanban board represent the stages of work in a project. Each column can have one or more statuses mapped to it. To move an issue from one column to another, you need to drag and drop it to a column that has a different status mapped to it. If the statuses are mapped to the same column, you cannot move the issue by dragging it on the board, but you can still use the workflow button to change its status.
Configuring columns, Moving an issue
The MR manager is unsure whether she wants a Scrum or Kanban board for her project. Identify one difference between the boards.
Answer(s): E
One difference between Scrum and Kanban boards is that only Scrum boards support selecting an estimation method. Estimation is a way of measuring how much work is required to complete an issue or a sprint. Scrum boards allow you to choose between story points, original time estimate, or issue count as estimation methods. Kanban boards do not have estimation methods, as they focus on managing the flow of work rather than planning sprints.
Configuring estimation and tracking, Estimating an issue
An issue was created with the following attributes:· Issue type: Story· Priority: Blocker· Labels: Tools, DevOps· Reporter: A.GrantAn excerpt of the board's swimlane configuration is shown.In which swimlane will the issue appear?
Answer(s): B
The issue will appear in the Expedite swimlane, because it matches the query priority = Blocker. Swimlanes are used to group issues on the board based on a common attribute, such as assignee, epic, or a custom query. The board's swimlane configuration shows that the first swimlane is Expedite, which has the query priority = Blocker. This means that any issue with a blocker priority will be placed in this swimlane, regardless of its other attributes. The other swimlanes have different queries that do not match the issue's attributes, such as type, labels, or reporter. Therefore, the issue will not appear in those swimlanes. The last swimlane is Everything Else, which is the default swimlane for any issue that does not match any of the previous queries. However, since the issue matches the Expedite query, it will not fall into this swimlane either. Hence, the correct answer is B.
[Configuring swimlanes], [Using swimlanes]
Your Scrum board has the following filter query:project in (ENG. DEV) and type in (Bug. Task) ORDER BY Priority ASC You have the necessary permissions but you are unable to drag an issue into a future sprint in the backlog.
Answer(s): D
The reason why you are unable to drag an issue into a future sprint in the backlog is that ranking is disabled. Ranking is a feature that allows you to order issues based on their relative priority or importance. Ranking is enabled by adding "ORDER BY Rank ASC" or "ORDER BY Rank DESC" to your board filter query. Ranking is required for Scrum boards, as it determines the order of issues in your backlog and sprints. If ranking is disabled, you cannot drag and drop issues in your backlog or plan future sprints.
Ranking an issue, Configuring filters
Share your comments for ATLASSIAN ACP-610 exam with other users:
sap c_ts450_2021
nice questions
ecellent materil for unserstanding
good so far
this is way too informative
very helpfull
q.189 - answers are incorrect.
awesome job in getting these questions
i cant find aws certified practitioner clf-c01 exam in aws website but i found aws certified practitioner clf-c02 exam. can everyone please verify the difference between the two clf-c01 and clf-c02? thank you
grazie mille. i got a satisfactory mark in my exam test today because of this exam dumps. sorry for my english.
some of the answers are incorrect. need to be reviewed.
so far so good
i am really liking it
thanks good stuff
need dump c_tadm_23
next time i will write a full review
first time using this site
please sent me oracle 1z0-1105-22 pdf
very helpful
good info about oml
very useful to practice
this website is very helpful.
good content
so challenging
17 should be d ,for morequery its scale out
nice question
yes.
good mateial
good practice exam
impressivre qustion
questions seem helpful
question 21 answer is alerts
am preparing for exam
Keeping this site free takes real effort. We constantly battle automated scraping and unauthorized content copying. A quick account helps us protect the community and keep the site free.
To continue studying for your ACP-610, please sign in or create a free account.