Jira Issues: Create Bugs, Assign, Transition & Log Work

How to Create a Bug in Jira?

A bug in Jira represents a defect or issue in the application under test. It is a type of issue used to report problems, failures, or unexpected behavior in the software.

Steps to Create a Bug (Web Interface)

1. Log in to Jira

Open your Jira project dashboard and navigate to the correct project where the bug should be created.

2. Click the Create Button

Click the Create button on the top navigation bar.

3. Fill in the Bug Details

Complete the Create Issue form with:

• Summary

• Steps to Reproduce

• Expected Result

• Actual Result

• Environment

• Priority

• Attachments

4. Click Create

Jira assigns a unique Issue Key (for example, PROJ-107) to the bug.

Interview Answer

"To create a bug in Jira, I click on the 'Create' button, choose the issue type as 'Bug', and provide details such as summary, steps to reproduce, expected vs actual results, environment, and priority. I also attach any supporting screenshots or logs. Once submitted, it gets tracked with a unique ID and assigned for resolution."

Scenario-Based Add-on

"In our project, whenever I find a UI or functional issue during regression, I capture the exact steps and environment, reproduce it twice, attach screenshots, and then log it in Jira with priority based on impact. I always assign it to the developer after discussing it on Slack or in a daily stand-up."

What are Components in Jira?

In Jira, components are subsections or categories of a project used to organize issues (bugs, tasks, or stories) by functional area, team, or module.

Think of components as folders within a project that help classify and manage issues more effectively.

Why Use Components?

Components help you:

• Group related issues by feature, module, or team.

• Filter and search issues easily.

• Assign default assignees based on the component.

• Generate component-wise reports to track work.

How Components Help in Real Projects

• Assign default developers or QA to components.

• Filter bugs by component (for example, Login).

• View component-wise progress on dashboards.

Where to Add or View Components

Navigate to:

Project Settings → Components → Create Component

Define:

• Name (for example, Payment)

• Description (Optional)

• Default Assignee (Optional)

Interview Answer

"In Jira, components help us divide a project into logical modules like 'Login', 'Payment', or 'API'. I use components to categorize issues properly so they're easier to track and assign. For example, if I find a bug in the checkout process, I tag it under the 'Cart' or 'Payment' component. This helps the team track and resolve issues more efficiently."

Scenario-Based Add-on

"In my last project, we used components like 'UI', 'Backend', and 'Security'. This helped assign bugs directly to the right team. It also simplified our daily stand-ups and bug triage meetings because we could filter and review issues component-wise."

How to Assign and Reassign Issues

Assigning an issue means assigning a task (bug, story, task, etc.) to a specific team member responsible for completing or resolving it.

Method 1 — From the Issue View

1. Open the issue.

2. Find the Assignee field.

3. Click the field.

4. Start typing the team member's name or email.

5. Select the correct user.

6. Click Update (or press Enter, depending on your Jira configuration).

Method 2 — From the Backlog or Board

1. Open the Backlog or Active Sprint Board.

2. Locate the issue.

3. Click the assignee avatar.

4. Select the appropriate team member.

How to Reassign an Issue

Simply change the Assignee field to another user.

Common reasons include:

• Task is blocked.

• A teammate is unavailable.

• Another developer has the required expertise.

Permissions Note

You must have the Assign Issue permission in Jira.

Typical users include:

• Project Administrators

• Scrum Masters

• Test Leads

• Team Members with appropriate permissions

Best Practices

• Don't assign too many issues to one person.

• Keep Jira updated.

• Use labels or components for categorization.

• Review unassigned issues during backlog grooming.

Interview Answer

"Assigning issues in Jira is simple but important. I go to the issue, click the Assignee field, and select the right team member. This helps ensure accountability. We typically assign tasks during sprint planning or daily stand-up based on workload and skill set."

What is a Transition in Jira?

A transition in Jira is the movement of an issue from one status to another within a workflow.

In simple terms, a transition is the bridge that moves a task forward in its lifecycle.

Real-world Example

"In my last project, when I logged a bug in Jira, the status was 'To Do'. Once the developer started work, they transitioned it to 'In Progress'. After code changes, they moved it to 'Code Review', and finally QA transitioned it to 'Done' after testing."

Interview Answer

"A transition in Jira is the action that moves an issue from one status to another in a workflow. For example, when a developer starts working on a task, they transition it from 'To Do' to 'In Progress'. These transitions help track the exact progress of each issue."

What is a Status in Jira?

In Jira, a status refers to the current state of an issue as it moves through its lifecycle in a workflow.

It represents where an issue is at a particular point in time, such as:

• To Do

• In Progress

• Code Review

• Done

Status vs Workflow

Example Workflow

To Do
   ↓
In Progress
   ↓
Code Review
   ↓
Done

Meaning of Each Status

• To Do – Ready to start.

• In Progress – Work is underway.

• Code Review – Code is under review.

• Done – Work has been completed.

Real-world Scenario

When a new bug is reported:

• Status = To Do

• Developer starts work → In Progress

• Code submitted → Code Review

• QA verifies the fix → Done

Bonus

Jira administrators can create custom statuses based on project requirements.

In Progress and Done are the most commonly used statuses in Agile projects.

Interview Answer

"A status in Jira refers to the current stage or state of an issue in its lifecycle. For example, if a bug is in development, its status might be 'In Progress', and when it's completed, its status might change to 'Done'. The status helps teams track the issue's progress within a workflow."

How to Move a Ticket Between Statuses

Every Jira issue follows a workflow consisting of predefined statuses connected by transitions.

Step-by-Step

1. Open the Ticket

Navigate to the issue.

2. Check the Current Status

The current status appears at the top of the issue.

Examples:

• To Do

• In Progress

• Done

3. Click the Transition Button

Jira displays the available workflow actions.

Example:

• Start Progress

4. Select the Desired Status

Choose the appropriate transition.

Examples:

• Start Progress → In Progress

• Resolve Issue → Done

5. Provide Additional Information (Optional)

Some workflows require:

• Comments

• Resolution

• Reassignment

6. Confirm the Transition

Click Update or Transition.

Real-time Example

Tester Logs Bug
        ↓
To Do
        ↓
Developer Starts Progress
        ↓
In Progress
        ↓
Submit for Review
        ↓
Code Review
        ↓
QA Verification
        ↓
Done

Interview Answer

"In Jira, each issue follows a predefined workflow. To move a ticket from one status to another, we perform a transition. For example, when I start working on a task, I click 'Start Progress' to change the status from 'To Do' to 'In Progress'. These transitions are controlled by the workflow configured by the admin. Sometimes we also provide comments or resolution details during a transition, especially when moving to Done or Closed."

How to Log Work and Track Time

Logging work means recording the amount of time spent working on an issue.

This helps with:

• Time Tracking

• Project Estimation

• Billing

• Resource Planning

Steps to Log Work

1. Open the Jira Ticket

Navigate to the issue.

2. Click More (or the Three Dots)

Open the issue menu.

3. Select Log Work

The Log Work dialog opens.

4. Enter Work Details

Provide:

• Time Spent (for example, 2h, 30m, 1d 3h)

• Date Started

• Remaining Estimate

5. Add a Comment (Optional)

Describe the completed work or any blockers.

6. Click Log

The work entry appears in the Work Log section.

Real-time Example

Example:

• Time Spent = 3h

• Date Started = 13-May-2025 10:00 AM

• Remaining Estimate = Auto-adjust

• Comment = "Debugged and fixed null pointer exception."

The work log is then recorded under the issue.

How Time is Used in Jira

Additional Tips

• Jira administrators can enable or disable Time Tracking.

• View logged work under the Time Tracking section.

• Reports include:

  • Time Tracking Report

  • Work Log Report

• Some organizations use Tempo Timesheets for advanced approvals and reporting.

Interview Answer

"In Jira, I log my daily work using the 'Log Work' feature available on every issue. It helps track time spent on tasks and provides the team with visibility. For example, after working on a bug fix for 2 hours, I open the issue, click 'Log Work', input '2h' as time spent, and optionally update the remaining estimate. This is useful for sprint planning and generating reports on team performance and project timelines."

A Bug Report Developers Can Act On

The summary alone tells a developer where, what and when; the frequency and network evidence save a round of "can't reproduce". Link the bug to the story it affects.

Logging Work: Time Format

Jira's time fields use a short format: 30m, 2h, 1d 4h, 1w. By default Jira counts 1d = 8h and 1w = 5d (administrators can change this), so "3d" means 24 working hours, not 72. Log work against the issue you actually worked on — testing time on the story, investigation time on the bug — so reports reflect where the effort went.

Practice Jira questions — creating and triaging bugs, workflows, JQL — under interview conditions in the Jira Interview Simulator. Related: Defect Bug Management.

📚 Official documentation: Jira Cloud documentation (Atlassian) · ISTQB Glossary of testing terms

FAQs

1. How do you create a bug in Jira?

• Open the project.

• Click Create.

• Select Bug.

• Fill in:

  • Summary

  • Steps to Reproduce

  • Expected Result

  • Actual Result

  • Environment

  • Priority

  • Attachments

• Click Create.

Jira assigns a unique Issue Key.

2. What are Components in Jira?

Components are project subdivisions used to organize issues by:

• Module

• Feature

• Team

They also support filtering, default assignees, and reporting.

3. How do you assign an issue to a team member?

Open the issue.

Click the Assignee field.

Select the team member.

Alternatively, assign directly from the Backlog or Board.

4. What is a Transition in Jira?

A transition is the action that moves an issue from one workflow status to another.

5. What is the difference between a Status and a Workflow?

6. How do you move a ticket from one status to another?

• Open the issue.

• Click the available transition.

• Add comments or resolution if required.

• Confirm the transition.

7. How do you log work or track time in Jira?

Open the issue.

Choose Log Work.

Enter:

• Time Spent

• Date Started

• Remaining Estimate

Optionally add a comment, then click Log.