The dictionary defines “issue” as “an important topic or problem for debate or discussion”. In Jira however, an “issue” represents all types of requests including: things to do, tasks, bugs and defects, new features, improvements, changes, incidents, tickets, problems, etc.
Another popular query is “What are the different types of JIRA issues?”.
Different organizations use Jira to track different kinds of issues, which can represent anything from a software bug, to a project task, or a leave request form. Issues are the building blocks of any Jira project. An issue could represent a story, a bug, a task, or another issue type in your project.
Issue keys are unique identifiers for every piece of work you track with Jira. They are easily recognizable and quick to remember. Issue keys are made up of two parts: Project keys are a series of alphanumberic characters that describe to people across your Jira site what pieces of work are related to your project.
JIRA is an issue tracking product or a software tool developed by Atlassian, commonly used for bug tracking, project management and issue tracking; it is entirely based on this three aspects.
How do I edit or delete a Jira issue?
Created by JIRA Software – do not edit or delete. Task − A task that needs to be done to achieve team’s goal. If a user logs in as Admin and navigate to Settings → JIRA Administrator → Issues, all the listed issue types will display.
Each Jira issue has a unique key in the format: KEY-123. Why the confusion? Teams have their own internal initiatives or strategic priorities they often call “projects.” Yet in Jira, a collection of issues is also called a project! For example, the Marketing team’s many internal projects are tracked in their one Jira project.
What is a parent issue in Jira?
By default, Jira supports three levels of hierarchy: Parent issues (or epic issues) represent high-level initiatives or bigger pieces of work in Jira. For software teams, a parent issue (or epic issue) may represent a new feature they’re developing.
For business teams, parent issue may represent major deliverables or phases of a project. Standard issues represent regular business tasks. In Jira, standard issues are where daily work is discussed and carried out by team members.
Why do I get these resolutions by default in Jira?
If you have Jira Software, you also get these resolutions by default: All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. Reading the code produces no clues as to why this behavior would occur. If more information appears later, please reopen the issue.