Issue Type – a classification of issues in a Jira project Projects are often set up per department, per team, or to track large initiatives with a known end date. Think of a Jira project is a bucket that contains a “to do” list. 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. Each Jira issue has a unique key in the format: KEY-123. Requests like “ I need a new desk phone” is an issue just like “ Create a new product” and “ The server is down!” are issues.
An issue is a single unique record of any type, regardless of its content or the scenario. 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. Why the confusion? The dictionary defines “issue” as “an important topic or problem for debate or discussion”. Here are three fundamental Jira terminology concepts to understand: Further, your organization may have introduced additional custom naming or language translations, which can add to the confusion. Some of the naming reflects its origins and the need for somewhat generic terminology so it can support #allthethings.
Generic terminology for pulpmotion software#
Jira began as a bug tracking tool for software development teams and morphed into an issue tracker and project management tool for all teams. Jira terminology is strange at first and even foreign if you’re using Jira to track business processes. What is a Jira issue and a Jira project? Why are users often confused by these terms? Why are things named the way they are? Answer
0 kommentar(er)
