When might you use "blocks" as an issue link type in JIRA?
- When an issue is a duplicate of another
- When one issue is dependent on another to proceed
- When two issues are similar
- When two issues are unrelated
"Blocks" might be used as an issue link type in JIRA when one issue is dependent on another to proceed. This means that the completion of the blocking issue is required before work can continue on the blocked issue. It represents a dependency relationship between the two issues.
In JIRA, what is the primary difference between a "Bug" and an "Epic" issue type?
- A "Bug" is a high-priority issue, while an "Epic" is a low-priority issue.
- A "Bug" is automatically assigned to developers, while an "Epic" is assigned to project managers.
- A "Bug" is only applicable to software development projects, while an "Epic" can be used in any project type.
- A "Bug" represents a defect or an issue in the software, whereas an "Epic" is a large body of work that can be broken down into smaller tasks.
In JIRA, a "Bug" is typically used to track defects or problems in the software that need to be fixed, whereas an "Epic" is used to represent a large body of work that can be broken down into smaller tasks, usually spanning multiple sprints or iterations. Bugs are usually more granular and focused, while Epics are broader in scope and often represent major features or initiatives within a project.
What is the primary purpose of customizing an Agile board in JIRA?
- Add or remove users from accessing the board
- Customize the layout and appearance of the board
- Define rules for issue ranking on the board
- Modify the workflow and issue statuses on board
Customizing an Agile board in JIRA allows teams to tailor the board's layout and appearance to suit their specific project needs, such as organizing and prioritizing tasks according to their workflow and preferences.
JIRA allows you to create custom _______ to filter issues for specific reporting needs.
- Dashboards
- Filters
- Reports
- Workflows
JIRA filters enable users to narrow down and tailor views of issues based on specific criteria, aiding in reporting and analysis.
How can you search for issues assigned to a specific user in JIRA?
- Navigate to User Profile > Assigned Issues
- Use the JIRA filter with assignee field
- Use the JIRA search bar and type "assignee: username"
- Use the JIRA search bar and type "user: username"
To search for issues assigned to a specific user in JIRA, you can use the JIRA search bar and type "assignee: username". This will filter the issues and display only those assigned to the specified user.
What is a project role in JIRA, and how does it impact project administration?
- A project role assigns tasks to team members
- A project role defines a set of permissions
- A project role determines the project's workflow
- A project role monitors project progress
In JIRA, a project role defines a set of permissions that determine what actions a user with that role can perform within the project. These permissions may include creating, editing, assigning, or transitioning issues, as well as administering the project settings. Project roles play a crucial role in project administration by allowing administrators to control access and responsibilities for different stakeholders. By assigning appropriate roles to users or groups, the administrator ensures efficient collaboration and adherence to project workflows and policies.
In the context of Agile boards, what is the purpose of setting up "Card Layout"?
- To assign team members to specific tasks.
- To configure the swimlane settings.
- To customize the appearance of cards on the board, including which fields are displayed.
- To define the workflow stages for your Agile process.
Setting up "Card Layout" in the context of Agile boards allows you to customize the appearance of cards on the board, including which fields are displayed. This can help provide relevant information at a glance and streamline the team's workflow by displaying essential details directly on the board.
Explain the steps involved in disaster recovery planning for JIRA system maintenance.
- Incident Response Plan
- Regular Backups
- Server Reboot Procedure
- User Training
Regular backups ensure that critical data in JIRA is preserved and can be restored in case of system failures, aiding in disaster recovery efforts.
What is a "smart value" in JIRA Automation, and how is it used?
- A feature that predicts user actions based on historical data.
- A placeholder that dynamically fetches values from JIRA fields.
- A tool for automating repetitive tasks in JIRA.
- An algorithm that optimizes workflow efficiency in JIRA.
In JIRA Automation, a "smart value" is a placeholder that dynamically fetches values from JIRA fields such as issue summary, assignee, or custom fields. It allows for dynamic content generation in automation rules, enabling users to create more flexible and powerful automation workflows.
Issue naming conventions should be documented and shared with the _______.
- competitors
- customers
- stakeholders
- team
Documenting and sharing issue naming conventions with stakeholders ensures everyone is on the same page, promoting consistency and understanding within the team and across the project.
JIRA Service Desk allows you to create customized _______ for different types of service requests.
- Dashboards
- Forms
- Reports
- Workflows
JIRA Service Desk allows you to create customized Forms for different types of service requests. These forms can be tailored to gather specific information required to process different types of requests effectively.
Scenario: You are a Scrum Master, and your team is consistently achieving a flat line on the Sprint Burndown Chart. What actions would you take to address this situation?
- Encourage the team to work harder to complete tasks more quickly.
- Ignore the flat line as it indicates stability and predictability.
- Increase the number of user stories in the sprint backlog to keep the team busy.
- Investigate any impediments or blockers hindering the team's progress.
A flat line on the Sprint Burndown Chart suggests that the team is not making progress towards completing the sprint backlog. As a Scrum Master, it's essential to investigate any impediments or blockers that may be hindering the team's progress. Addressing these issues and providing support can help the team overcome obstacles and regain momentum towards achieving their sprint goals.