What is the difference between "Edit" and "Transition" when making changes to an issue's status?
- "Edit" allows users to delete an issue, while "Transition" allows users to add comments
- "Edit" allows users to modify the details of an issue, while "Transition" changes the workflow status of an issue
- "Edit" and "Transition" are two terms for the same action in JIRA
- "Edit" and "Transition" both change the workflow status of an issue but in different ways
In JIRA, "Edit" allows users to modify the details of an issue, such as the summary, description, assignee, etc., without changing its workflow status. On the other hand, "Transition" is used to change the workflow status of an issue, moving it from one status to another in the workflow. This typically represents progress in the issue's lifecycle, such as from "Open" to "In Progress" or from "In Progress" to "Resolved".
JIRA workflows can include _______ to automatically perform actions after transitions.
- Conditions
- Post Functions
- Triggers
- Validators
JIRA workflows utilize Post Functions to execute actions automatically after transitions. These functions can range from sending notifications to updating fields or triggering external processes, enhancing workflow automation and streamlining issue management processes.
What is "Velocity" in the context of Agile reporting, and how is it calculated in JIRA?
- Velocity indicates the speed of the internet connection
- Velocity measures the number of bugs fixed in a release
- Velocity represents the amount of work a team can complete in a sprint
- Velocity signifies the number of users accessing the JIRA instance
Velocity, in the context of Agile reporting, represents the amount of work a team can complete in a sprint based on historical data. It helps teams estimate their capacity and plan future sprints effectively. In JIRA, velocity is calculated by summing up the estimation points of all completed user stories or tasks in a sprint.
In JIRA, a sub-task is often used to break down a larger issue into smaller _______.
- components
- stories
- sub-tasks
- tasks
In JIRA, a sub-task is used to break down a larger issue into smaller, more manageable tasks. Sub-tasks are essentially smaller units of work that contribute to the completion of the parent issue.
The y-axis of a Burndown Chart usually represents _______.
- Time
- Story Points
- Tasks
- Effort Remaining
The correct option is Effort Remaining. In a Burndown Chart, the y-axis typically represents the amount of effort remaining to complete the work. This could be measured in various units such as story points, hours, or tasks. It provides a visual indication of the progress made towards completing the sprint backlog.
Scenario: In your JIRA project, you have a parent issue representing a feature, and you want to track the development tasks required to complete that feature. What type of issues would you create to represent these development tasks, and how would you link them to the parent issue?
- Sub-tasks
- Epics
- Stories
- Tasks
Option 1: "Sub-tasks" is the correct option. When you have a parent issue representing a feature in JIRA and need to track the development tasks required to complete that feature, you create sub-tasks. Sub-tasks break down the parent issue into smaller, manageable tasks, each representing a specific aspect of the feature development. These sub-tasks are then linked to the parent issue, allowing for hierarchical organization and clear visibility into the progress of individual tasks contributing to the completion of the feature.
In Agile Scrum, what is the purpose of the Sprint Review meeting?
- To discuss technical issues within the team.
- To estimate the effort for upcoming tasks.
- To plan the next sprint backlog.
- To review and demonstrate completed work to stakeholders.
The Sprint Review meeting in Agile Scrum serves the purpose of showcasing the completed work to stakeholders for feedback and validation. It allows stakeholders to provide input, which can influence future product increments. This transparency promotes collaboration and ensures alignment with stakeholders' expectations.
Which of the following is a recommended approach for naming issues in JIRA?
- Use cryptic titles to encourage curiosity
- Use descriptive titles that clearly indicate the issue's content
- Use emoji-filled titles for visual appeal
- Use generic titles to cover a broad range of topics
In JIRA, using descriptive titles that clearly indicate the issue's content is a recommended approach. This helps users quickly understand the nature of the issue without having to delve into the details. Clear and concise titles facilitate efficient communication and collaboration within the team.
To restrict access to certain actions in JIRA, you can use _______.
- Issue types
- Permission schemes
- User groups
- Workflow schemes
In JIRA, permission schemes are used to control access to various actions and features within the system. These schemes define who can perform which actions on different aspects of JIRA projects and issues.
In JIRA, what types of actions can be performed using Bulk Operations?
- Comment, log work, re-open, attach files
- Create, close, assign, link, watch
- Delete, resolve, assign, prioritize
- Edit, transition, move, clone, delete, watch
In JIRA, Bulk Operations allow users to perform actions like editing multiple issues' fields at once, transitioning multiple issues through workflow states, moving multiple issues to another project, cloning issues, deleting multiple issues, and more.