❔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.