面试题与答案

JIRA is a popular issue tracking and project management tool used for bug tracking, issue tracking, and project management. It is widely used in software development to manage and track project progress.

Example:

JIRA is used to create, track, and manage issues, as well as to plan and track the progress of projects.

Issues in JIRA can be linked by using the 'Link' option in the issue view. There are various types of links, such as 'blocks,' 'is blocked by,' 'is duplicated by,' etc.

Example:

You can link two issues to show a relationship, such as marking one issue as blocking another.

The JIRA dashboard can be customized by adding gadgets. Gadgets are small, dynamic content modules that can be added to the dashboard to display information such as project progress, recent issues, etc.

Example:

You can customize your dashboard by adding gadgets like 'Assigned to Me,' 'Recently Created Issues,' and 'Burndown Chart.'

A Bug in JIRA represents a defect or an issue in the software, while a Task is a piece of work that needs to be done. Bugs are typically associated with fixing issues in the code, while tasks are broader work items.

Example:

A bug might be 'Application crashes on login,' while a task could be 'Implement user authentication.'

Sub-tasks in JIRA are created within the context of a parent issue. You can create a sub-task by going to the 'More' menu on an issue and selecting 'Create Sub-Task.'

Example:

If the parent issue is 'Develop Feature X,' a sub-task could be 'Write Unit Tests for Feature X.'

Bulk updates in JIRA allow you to perform the same operation on multiple issues simultaneously. You can use the 'Bulk Change' option from the issue navigator to update fields, transition issues, or delete issues in bulk.

Example:

Bulk update could be used to close multiple issues that share a common resolution.

JIRA allows users to set up notifications to receive updates on specific events, such as issue creation, comments, or status changes. Users can customize their notification preferences from the user profile settings.

Example:

A developer might set up notifications to receive emails when assigned to an issue or when the issue status changes.

Custom fields in JIRA are created by administrators to capture specific information. To create a custom field, go to the 'Issues' menu, select 'Field Configurations,' and then choose 'Add Custom Field.'

Example:

A software team might create a custom field 'Release Version' to track the target release for each issue.

To set up a JIRA Scrum Board, go to the 'Boards' menu, select 'Create Board,' and choose 'Scrum.' Define the filter that includes the issues you want to display on the board and configure the board settings.

Example:

A Scrum Board might include columns like 'To Do,' 'In Progress,' and 'Done' to visualize the flow of work during a sprint.

To create a filter in JIRA, navigate to the 'Issues' menu, select 'Manage Filters,' and then click 'Create Filter.' Define the filter criteria based on project, status, or other parameters.

Example:

A filter could be 'All Open Bugs assigned to Me,' helping a developer focus on their current tasks.

JIRA Agile Quick Filters are used to quickly filter and narrow down the issues displayed on Agile Boards. They provide a convenient way to focus on specific sets of issues based on criteria such as assignee, status, or label.

Example:

A Quick Filter could be set up to show only the issues assigned to the current sprint, helping the team focus on the work at hand.

An issue in JIRA represents a task, bug, or new feature, while a project is a collection of issues. Projects help organize and manage related tasks.

Example:

In a software development project, issues could include tasks like coding, testing, and documentation, while the project encompasses all these tasks.

A JIRA Workflow is a set of statuses and transitions that an issue goes through during its lifecycle. It defines how an issue moves from creation to completion.

Example:

A simple workflow might include statuses like 'Open,' 'In Progress,' 'Resolved,' and 'Closed,' with transitions between them.

Components in JIRA are sub-sections of a project. They are used to group issues within a project based on a common feature or functionality.

Example:

In a software project, components could be 'Frontend,' 'Backend,' and 'Database,' helping to categorize and manage issues more efficiently.

A JIRA Epic is a large body of work that can be broken down into smaller tasks. It is used to plan, track, and manage work on a larger scale.

Example:

In an agile software development project, an Epic might represent a major feature or user story that requires multiple sprints to complete.

The JIRA Agile Board is used in agile projects to visualize and manage the flow of work. It provides a visual representation of the work being done and helps teams collaborate more effectively.

Example:

An Agile Board might include columns like 'To Do,' 'In Progress,' 'Done,' and allow team members to drag issues between these columns.

JIRA Service Desk is designed for service and support teams, while JIRA Software is tailored for software development teams. Service Desk focuses on incident management, problem management, and service requests.

Example:

A software development team might use JIRA Software to manage coding tasks, while a support team might use JIRA Service Desk to handle customer issues.

A JIRA Sprint is a time-boxed period during which a specific set of work is completed. It is a fundamental concept in agile methodologies and helps teams plan and execute their work in iterations.

Example:

A sprint could last two weeks, during which the team aims to complete a defined set of user stories and tasks.

Story Points are a relative estimation of the effort required to complete a user story. It is a unit of measure used by agile teams to estimate and plan the amount of work involved.

Example:

A team might use a Fibonacci sequence (1, 2, 3, 5, 8, 13) to assign story points to user stories, indicating the level of complexity.

JIRA Marketplace is an online marketplace where users can find and install apps and add-ons to extend the functionality of JIRA. It allows users to customize and enhance their JIRA instance based on their specific needs.

Example:

Teams might use JIRA Marketplace to add integrations, reporting tools, and additional features to their JIRA environment.

JIRA integrates with version control systems like Git through plugins or add-ons. This integration allows for better traceability between code changes and the corresponding JIRA issues.

Example:

Commits in Git can be linked to JIRA issues, providing a comprehensive view of code changes in the context of project tasks.

JIRA Agile Reports provide visual insights into project progress and team performance. Examples include Burndown Charts, Velocity Charts, and Sprint Reports.

Example:

A Burndown Chart visually represents the work completed versus the work remaining in a sprint, helping teams track their progress.

The JIRA Administrator role is responsible for managing and configuring the JIRA instance. Administrators have the authority to customize workflows, schemes, permissions, and other system settings.

Example:

An administrator might configure JIRA to match the specific needs and processes of a development team.

Permission Schemes in JIRA define the permissions that control what actions users and groups can perform on issues and other resources. They are associated with projects to regulate access.

Example:

A Permission Scheme might grant 'Browse Projects' permission to all users and 'Close Issues' permission only to a specific group.

The JIRA Backlog is a prioritized list of work items, often in the form of user stories or tasks, that the team plans to address in future sprints. It helps the team focus on what needs to be done next.

Example:

The backlog might include user stories like 'Implement Login Page' and 'Optimize Database Queries.'

JIRA provides built-in support for Agile methodologies through features like Agile Boards, Backlogs, and Sprints. It allows teams to plan, track, and manage work using Scrum or Kanban practices.

Example:

A Scrum team might use JIRA to create and manage sprints, while a Kanban team might use the Backlog and Board to visualize work in progress.

JIRA Marketplace is an online marketplace where users can find and install apps and add-ons to extend the functionality of JIRA. It allows users to customize and enhance their JIRA instance based on their specific needs.

Example:

Teams might use JIRA Marketplace to add integrations, reporting tools, and additional features to their JIRA environment.

Issue Security Levels in JIRA allow administrators to control who can view and edit specific issues. They can be set at the project level and restrict access to sensitive information.

Example:

An issue related to a security vulnerability might have a high-security level, limiting access to a specific group of users.

JIRA Roadmaps provide a visual representation of the planned and scheduled work over time. They help teams and stakeholders understand the project timeline and key milestones.

Example:

A roadmap might include upcoming sprints, releases, and major features, giving a high-level overview of the project's progress.

JIRA Query Language (JQL) is the query language used to perform complex queries in JIRA. It allows users to create custom filters to find specific sets of issues based on various criteria.

Example:

A JQL query could be 'project = MyProject AND status = Open' to find all open issues in a specific project.