โ”Interview Questions

๐ŸŒ What is Jira?

Jira is an issue-tracking and project-management tool developed by Atlassian. It is commonly used by Agile development teams to plan and track their work.

๐Ÿ“‹ What can you use Jira for?

โœ… Issue and bug tracking

โœ… Agile project management

โœ… Task board for sprints

โœ… Kanban workflows

โœ… Time tracking

โœ… Reporting and analytics

๐Ÿƒ How can teams use Jira for Agile?

๐Ÿ”˜ Teams can create projects, epics, stories, and tasks in Jira to represent their product backlog.

๐Ÿ”˜ They can then plan sprints by assigning stories and tasks to the sprint.

๐Ÿ”˜ Jira provides digital task boards to visualize the work and track progress.

๐Ÿ”˜ Members update their status and log time against their tasks.

๐Ÿ”˜ Teams can incorporate feedback and implement changes in future sprints.

๐Ÿ˜บ What are the main Jira terminologies?

๐Ÿ”˜ Projects

๐Ÿ”˜ Issues (represent tasks, stories, bugs)

๐Ÿ”˜ Epics (represent higher-level features or themes)

๐Ÿ”˜ Statuses (to, in progress, done, etc.)

๐Ÿ”˜ Assignees

๐Ÿ”˜ Comments

๐Ÿ”˜ Links (between related issues)

๐Ÿ”˜ Transitions (between statuses)

๐Ÿ—“ How does Jira help with sprint planning?

๐Ÿ”˜ Jira allows teams to create sprints as "issues" within a project.

๐Ÿ”˜ Teams can drag and drop stories and tasks from the backlog onto a sprint.

๐Ÿ”˜ They can set a start and end date for the time-boxed sprint.

๐Ÿ”˜ Progress is visualized on sprint task boards and burn-down charts.

๐Ÿ”˜ Teams can track velocity and use it to plan future sprints.

So in summary, Jira provides a suite of tools to help Agile teams manage their issues, backlog, and sprints and track progress toward delivering working software.

โ“What is Jira used for?

โž• Jira is used for project and issue tracking.

๐Ÿ“ Manage bugs, tasks, features, changes and more.

๐Ÿ‘ฅAssign to teams and individuals

๐Ÿ”ขPrioritize using customized workflows

๐Ÿ“ˆTrack work and measure progress

๐Ÿค” What are the components of Jira?

๐Ÿšฉ Issues - Bugs, tasks, stories, etc.

๐Ÿ”ขProjects - Group-related issues

๐Ÿ‘ฅ Users - Assign issues to people

๐ŸŒ Dashboards - Visualize status

โš™๏ธ Components - Organize into parts

๐Ÿ”˜ Statuses - Track progress

๐Ÿ“ Comments - Communicate history

๐Ÿ“… Schedules - Plan releases

โœ… How can your workflow in Jira?

๐Ÿ”ƒ Customize statuses and transitions

๐Ÿ‘ฅ Add roles and assign them to groups

๐Ÿ“†Custom screens to view data

โฑ Automate using webhooks

๐Ÿ“ŠTrack using built-in reports

โœ… Integrate with other tools

โœ๏ธ Create customized fields

๐ŸงฎUse issue types and priorities

๐Ÿค– What automation is possible in Jira?

๐Ÿ”ƒ Status change triggers

๐Ÿ“… Due date reminders

๐Ÿ“จ Email notifications

๐Ÿ“ฃ Posts to Slack

๐Ÿ“ˆ Real-time dashboards

โœ…Webhook integrations

๐ŸŸข Issue creation

๐ŸŸ Assignments

โš ๏ธ Alerts for blockers

๐Ÿ”  How does searching work in Jira?

๐Ÿ“ Text search across fields

๐Ÿงฎ Filter by issue types, statuses

๐Ÿ‘ค Assignees, reporters

๐Ÿ’ฒ Priorities, labels

โ— Tags

๐Ÿ—“ Created/Updated dates

๐Ÿ˜ด JQL - powerful query language

โฐ How do you manage time in Jira?

โฐ Log work in issues

๐Ÿ“Š Track time spent

โฒ Set timers

๐Ÿ“… Deadlines

๐Ÿ“ˆ Check progress vs estimates

๐Ÿ“‰ Burn down/up charts

๐Ÿ“† Timeline gadgets

๐Ÿ—‚ Manage roadmaps

๐Ÿ—บ How do you plan releases in Jira?

๐Ÿ“ Define release issues

๐Ÿ’ฒ Prioritize based on business need

๐ŸŽฏ Set goals and acceptance criteria

๐Ÿ“… Define start/end dates

๐Ÿ‘ฅ Assign team members

๐Ÿ“Š Track progress using boards

โฑ Manage using roadmaps

๐Ÿ“ฃ Communicate status

โœ… Determine "done" criteria

๐Ÿ“‹ How do you create requirements in Jira?

๐Ÿ“ Write user stories

๐Ÿ”ข Assign story points

โœ Add acceptance criteria

๐Ÿงฎ Prioritize using the backlog

๐Ÿ‘ฅAssign teams to stories

๐Ÿ“ˆ Track progress

โœ”๏ธ Verify acceptance tests

๐Ÿ“link related requirements

โ™ป๏ธ Adjust as needed

๐Ÿงฉ How do you organize work in Jira?

๐Ÿ—„ Hierarchies - Epics, stories, tasks ๐Ÿ‘ฅ Teams

โš™๏ธ Components

๐ŸšฉIssue types

๐Ÿ’ฒ Priorities

๐Ÿšฉ Status

โ›ฝ Epics โ†’ Stories โ†’ Tasks ๐Ÿ”ขSequence flow

๐Ÿ”˜ Swimlanes

๐Ÿ’ป What integrations are possible with Jira?

๐Ÿ“ฆ With source code tools:

โœ… Git

โœ…GitHub

โœ…Bitbucket

๐Ÿงฐ With dev tools:

โœ…Jenkins

โœ…Bamboo

โœ…VS Code

๐Ÿ‘ฅWith team tools:

โœ… Slack

โœ…Confluence

โœ…Trello

โœ…Teams

๐Ÿ›  With testing tools:

โœ…Testrail

โœ…SauceLabs

โœ…Postman

How do you handle a blocked user story in JIRA?

๐Ÿงฎ The first step is correctly estimating user stories to avoid blocked stories. This includes:

๐Ÿ’ญ Thinking through dependencies

๐Ÿงฉ Considering risks upfront ๐Ÿ•ฐ Estimating time conservatively

โ™ป๏ธ Basing efforts on past stories

๐Ÿ‘ฅ Once a story is blocked:

โŒ Mark the status as blocked

๐Ÿ™… Assign it to the person blocking it

๐Ÿ’ฌ Add a detailed comment on the blocker

โณ To unblock the story:

๐Ÿ—ฃ Improve communication

๐Ÿš€ Remove dependencies

โœ… Fix integration issues

๐Ÿ› Resolve resource constraints

๐Ÿงฌ Fix data/infrastructure problems

๐Ÿงฎ While a story is blocked:

๐Ÿ”ข Reduce its story points

โŒ Stop tracking time spent on it

โ™ป๏ธ Re-prioritize the backlog ๐Ÿ’ซ Break it into smaller stories

๐Ÿ’ก To avoid future blockers:

๐Ÿง  Learn from past mistakes

โ™ป๏ธ Improve planning process โœ”๏ธ Verify dependencies early

๐Ÿค Strengthen handoffs

๐Ÿ”ƒ Adjust workflow as needed

โš™๏ธ With technical blockers:

๐Ÿ’ป Fix coding issues

โœ… Resolve integration problems ๐Ÿ’พ Fix data/DB inconsistencies ๐Ÿ›  Fix environment setup

๐Ÿงน In JIRA specifically:

โŒ Mark as blocked status

๐Ÿ“ข Communicate in comments ๐Ÿ“ Update description clearly

โ™ป๏ธ Re-estimate story points

๐ŸŽฏ Prioritize killing blockers

๐Ÿ’ฌ What is Zephyr for Jira?

Zephyr for Jira is an agile test management plugin for the Jira issue tracking software. It helps QA and testing teams plan, manage and track testing within an Agile workflow.

๐ŸŽฏ What does Zephyr for Jira do?

โœ… Creates test plans linked to Jira issues/stories

โœ… Defines test cases and assigns them to testers

โœ… Allows testers to log test results and defects against cases

โœ… Provides defect and test run tracking

โœ… Generates test coverage and analysis reports

โœ… Integrates with Jira activities like sprints and Kanban boards

๐Ÿž How does Zephyr integrate with Jira's defect tracking?

Zephyr seamlessly links test runs and defects logged during testing.

Testers can:

๐Ÿ”˜ Create defects directly from a test run in Zephyr

๐Ÿ”˜ Link existing Jira issues to test runs

๐Ÿ”˜ View related test runs from a defect in Jira

This provides end-to-end traceability from testing to defects.

๐Ÿ“ˆ What kinds of reports does Zephyr generate?

๐Ÿ‘‰๐Ÿผ Test coverage reports by test type, test plan, and tester

๐Ÿ‘‰๐Ÿผ Test run summaries

๐Ÿ‘‰๐Ÿผ Defect trend reports

๐Ÿ‘‰๐Ÿผ Requirements coverage

๐Ÿ‘‰๐Ÿผ Test environment performance

๐Ÿ”ฌ What features does Qality plugin add?

Qality plugin adds test case parametrization and data-driven testing:

๐Ÿ‘‰ Input and output parameters

๐Ÿ‘‰ Iterative test executions across data sets

๐Ÿ‘‰ Filtering and searching within data

๐Ÿ‘‰ Ability to define preconditions and expected results

๐Ÿ‘‰ Integrates data sets into the test management workflow

So in summary, the Zephyr and Qality plugins provide robust test management tools that integrate deeply with Jira's Agile workflows, giving QA and testing teams greater visibility and control.

Last updated

Was this helpful?