Scenario: In your JIRA project, you have identified a need to represent small, well-defined pieces of work that can be completed independently. Which issue type in JIRA would be most suitable for this purpose, and how does it differ from other issue types?
- Epic: This issue type allows for tracking large bodies of work that can be broken down into smaller tasks.
- Story: This issue type is suitable for tracking user stories or requirements.
- Sub-task: This issue type allows for breaking down larger tasks into smaller, manageable units of work.
- Task: This issue type is ideal for tracking small, actionable items.
The most suitable issue type for representing small, well-defined pieces of work that can be completed independently is a "Sub-task." Sub-tasks are used to break down larger tasks into smaller, manageable units, making them perfect for representing small pieces of work within a larger task. Unlike other issue types, sub-tasks are dependent on their parent tasks and cannot exist independently.
Agile teams often use _______ estimation to assign story points to user stories.
- Dot Voting
- Fibonacci
- Planning Poker
- T-shirt Sizes
The correct answer is "Fibonacci". Fibonacci sequence (1, 2, 3, 5, 8, 13, etc.) is commonly used in Agile for story point estimation. It allows for relative sizing of user stories, facilitating discussions and achieving consensus.
How can you initiate a manual backup in JIRA?
- By navigating to System > Backup Manager and selecting "Create Backup"
- By contacting Atlassian Support
- By scheduling a cron job to automatically backup data
- By exporting data to an external storage device
You can manually initiate a backup in JIRA by accessing the Backup Manager through the System menu and selecting the option to create a backup. This ensures that you have a recent copy of your JIRA data readily available for restoration if needed.
In Agile methodology, who is primarily responsible for prioritizing and managing the backlog?
- Development Team
- Product Owner
- Project Manager
- Scrum Master
In Agile methodology, the Product Owner is primarily responsible for prioritizing and managing the backlog. The Product Owner is the key stakeholder who represents the voice of the customer and is responsible for maximizing the value of the product. They work closely with stakeholders to understand requirements, prioritize features, and ensure that the backlog reflects the most valuable items to be worked on by the development team. The Scrum Master facilitates the process, while the development team contributes to refining and estimating backlog items.
JIRA provides a built-in custom field type called _______ that allows users to select values from a predefined list.
- Checkbox
- Radio Button
- Select List
- Text Field
In JIRA, the built-in custom field type "Select List" enables users to choose values from a predefined list. This is useful for maintaining consistency and ensuring data integrity within projects. Using a select list field helps standardize data entry and reporting across various issues.
A team member suggests integrating JIRA with a project management tool. How would you evaluate whether this integration is necessary and beneficial for your team?
- Assess the overlap of features and functionalities between JIRA and the project management tool
- Consider the impact on team workflows and productivity
- Evaluate the cost and resources required for integration and maintenance of both systems
- Seek feedback from team members on their preferences and pain points regarding issue tracking and project management tools
When considering integrating JIRA with a project management tool, it's essential to assess the overlap of features and functionalities between the two systems. If significant redundancy exists, the integration may not be necessary. Additionally, evaluating the impact on team workflows, cost, and resources required for integration and maintenance is crucial in determining the overall benefit to the team. Seeking feedback from team members can provide insights into their preferences and pain points, aiding in the decision-making process.
Scenario: You have received a request to update the priority of all open issues that are older than 30 days. How can you leverage Bulk Operations and JQL to accomplish this task?
- Clone Issues, and you would create duplicates of the issues with updated priority.
- Delete Issues, and you would remove the older issues and recreate them with updated priority.
- Move Issues, and you would navigate to the desired project and manually update the priority.
- Edit Issues, and you would use JQL to filter issues older than 30 days and then perform a Bulk Change to update their priority.
The correct option is to use "Edit Issues" as the Bulk Operation. By leveraging JQL to filter issues older than 30 days, you can identify the relevant set of issues. Then, using Bulk Change, you can efficiently update their priority to meet the requested criteria. This approach streamlines the process and ensures timely resolution of priority adjustments.
What is the difference between "global permissions" and "project permissions" in JIRA?
- Global permissions apply only to administrators, while project permissions apply to all users
- Global permissions apply to the entire JIRA instance, while project permissions are specific to individual projects
- Global permissions can be modified by project administrators, while project permissions cannot
- Global permissions control issue creation, while project permissions control issue editing
Global permissions in JIRA apply to the entire instance and are set by JIRA administrators. These permissions govern actions such as creating projects, administering users, and configuring system settings. Project permissions, on the other hand, apply to individual projects and govern actions within those projects, such as creating issues, editing issues, and managing project components.
In JIRA, where can you configure the location and settings for automated backups?
- System Administration section
- Backup Manager section
- Global Configuration page
- System Settings page
In JIRA, the location and settings for automated backups can be configured in the Backup Manager section. This section provides options for setting up automated backups, specifying the backup location, scheduling frequency, and retention policy.
JIRA Data Center uses a shared _______ to distribute user requests.
- Cache
- Cluster
- Network
- Server
JIRA Data Center employs a shared cluster to distribute user requests across multiple nodes, ensuring scalability, reliability, and high availability of the application.