issue

basicwidespread

An issue is a logged entry in a software project regarding a bug, idea, or task to be completed, which the team discusses, assigns, and eventually closes.

In plain terms

Imagine the fault-report book of an apartment building: someone writes that the tap on the third floor is dripping, the caretaker adds that they have called the plumber, and in the end it gets ticked off. An issue is the same thing in the world of software: a numbered entry saying that something needs to be dealt with.

An issue is not only a bug report. It can also be an idea for a new feature, a question, a task to be done or a missing description. The point is that the to-do item is not in an email or in someone's head, but in a shared, searchable place.

What distinguishes it from a simple to-do list is that discussion takes place under every issue: you can ask questions, attach screenshots, assign responsibility, and add labels. This way, even years later, it becomes clear why a decision was made.

In the AI era, it has taken on a new role: many teams now issue work to coding agents in issue format. The agent reads the description, writes the fix, and sends it back as a proposal for review.

How it works

Someone opens an issue: they give it a title and describe the problem or what they want. A good bug report also includes how to reproduce the bug.
The system assigns it a serial number (e.g., #482), the team labels it (bug, idea, urgent), and decides its priority.
A responsible party is designated, who can be a human or a coding agent, while details are clarified in the comments.
The responsible person makes the change and links it to the issue, so it is visible which code modification solves which problem.
If the fix is accepted, the issue is closed, or the system closes it automatically. It is not deleted, remains searchable at any time, and can be reopened if the bug recurs.

An everyday example

You notice that your favorite free note-taking program crashes when you paste an image. You open an issue on the program's GitHub page, describe what you did, and a few days later receive a notification that a developer fixed it and the post was closed.

Who is affected

developerMost of their daily work consists of issues: these tell them what to do and document what they have completed. → Code

entrepreneur, executiveFrom the list of issues, you can see without developer knowledge where your product stands, what is stuck, and where the team's time goes.

employeeIf you find a bug in corporate software, a well-written issue will get you a solution much faster than a hallway comment. → Work & HR

everyoneWith open-source programs, anyone can open an issue, so as a user you can also report a bug or request a new feature.

A common misconception

MythAz issue mindig azt jelenti, hogy valami elromlott a programban.

In realityAn issue is a broader concept: it can be a bug, but equally an idea, a question, a planned feature, or a simple task. Therefore, many open issues are not necessarily a sign of poor quality; often they indicate an active community.

Limits and risks

An issue is only as good as how precisely it is written: neither a human nor an agent can do anything with a "not working" type report.
Public issues are readable by anyone, so do not include passwords, customer data, or other confidential information.
Opening an issue is no guarantee of a solution: in open-source projects, volunteers work on them, and a request can remain open for years.
If a coding agent works from issues, the text of the entry can act as an instruction, so a maliciously written issue could be used to mislead it. The result must be reviewed by a human.

Similar, but not the same

bug – A bug is the software error itself, while an issue is the record tracking it, which may cover more than just errors.
pull request – An issue describes the problem or request, while a pull request contains the specific code changes that resolve it.
ticket – A ticket is typically a report from customer service or IT operations, while an issue is more a software development term, though they are often used interchangeably in daily life.

Related concepts

Broader

software development, projektmenedzsment, version control

Narrower

bug report, feature request

On the edge

bug, pull request, repository, commit, coding agent

A brief history

The systematic recording of bugs and tasks dates back almost to the beginning of software development. Among web-based bug trackers, Bugzilla appeared in 1998 and Jira in 2002. These systems already used the word "issue" ("issue tracking"), but GitHub, launched in 2008, truly made it part of the developers' common language.

Where things stand

At the end of 2026, the issue is the basic unit of work in software development, used by almost every team and open-source project. What is new is that in a growing number of places coding agents are also assigned issues and independently prepare fix proposals for them.

Status: 2026 November

In the news

Appears in 218 Agent Age stories; the curve shows weekly occurrence in the news magazine.

AWS launches Kiro bots to coordinate AI coding agentsNov 5, 2026 · Code
FCA to launch quantum machine learning pilot group in 2027 to tackle fraud and money launderingNov 5, 2026 · Money
Visa sets up six Singapore hubs for AI and next-generation paymentsNov 5, 2026 · Money
Oxford University Press links its content to ChatGPT Edu in three-month pilotNov 4, 2026 · Education & Family
OpenAI builds new Git backend Pando after Codex agents drive commit surgeNov 4, 2026 · Code
OCC's first supervisory guidance on bank AI use rates simple payment agents as high riskNov 4, 2026 · Money
Pliant raises $80M Series C to open B2B payments to AI agentsNov 4, 2026 · Money
MAS Future of Finance Institute starts operations in Singapore to speed up AI adoptionNov 3, 2026 · Money

Also known as

issue · issue-k · GitHub issue · hibajegy · feladatjegy · ticket · announcement

Sources

This entry was machine-edited and has undergone machine expert review; the “In the news” section updates automatically from Agent Age stories.