--- title: Stop misusing Jira issue types - here’s how to get them right description: What are Jira issue types and how should you use them effectively? Discover the hierarchy, types, and best practices to optimize your team’s workflow. image: https://resources.agileops.vn/hubfs/Blogs/BLOG-164/AgileOps%20-%20Jira%20issue%20types%202.png --- [![AgileOps - Logo AgileOps](https://resources.agileops.vn/hubfs/raw_assets/public/agileops-theme-v2/images/website-home-image/Fixed%20Header%20Logo.svg) ![AgileOps - Logo AgileOps](https://resources.agileops.vn/hubfs/raw_assets/public/agileops-theme-v2/images/website-home-image/Fixed%20Header%20Logo.svg)](https://agileops.vn/?hsLang=en) Services ![AgileOps - Atlassian Training Program](https://resources.agileops.vn/hs-fs/hubfs/Documents/ATP/Illus%20(4).png?width=480&height=336&name=Illus%20(4).png) Atlassian training Training program to help teams effectively apply Jira, Confluence, and other Atlassian tools. [Explore the courses](https://training.agileops.vn/en/atlassian?hsLang=en) [![AgileOps - Logo Atlassian](https://resources.agileops.vn/hs-fs/hubfs/Atlassian.png?width=48&height=48&name=Atlassian.png) Atlassian Transform business management with advanced software like Jira, Confluence, Jira Service Management,...](https://agileops.vn/en/services/atlassian?hsLang=en) [![AgileOps - Logo HubSpot](https://resources.agileops.vn/hs-fs/hubfs/HubSpot.png?width=48&height=48&name=HubSpot.png) HubSpot All-in-one platform for lead management, marketing, sales, and customer services](https://agileops.vn/en/services/hubspot?hsLang=en) [![AgileOps - Logo Google](https://resources.agileops.vn/hs-fs/hubfs/GG.png?width=60&height=48&name=GG.png) Google Gmail, Google Drive, Docs, Sheets, Slides, Calendar … - Unlock seamless and efficient collaboration for your business](https://agileops.vn/en/services/google-workspace?hsLang=en) [![AgileOps - Logo Kubernetes](https://resources.agileops.vn/hubfs/Kubernetes_logo_without_workmark.svg) Kubernetes Container orchestration platform that helps teams automate infrastructure, manage applications, and scale with ease](https://agileops.vn/en/services/kubernetes?hsLang=en) [![AgileOps - Salesforce](https://resources.agileops.vn/hs-fs/hubfs/Salesforce/Logo%20Ku%20(1).png?width=94&height=64&name=Logo%20Ku%20(1).png) Salesforce End-to-end customer management with Salesforce products - Sales Cloud, Service Cloud, and Marketing Cloud.](https://agileops.vn/en/services/salesforce?hsLang=en) [Atlassian training Training program to help teams effectively apply Jira, Confluence, and other Atlassian tools. Explore the courses ![AgileOps - Logo AgileOps](https://resources.agileops.vn/hubfs/raw_assets/public/agileops-theme-v2/images/website-home-image/Fixed%20Header%20Logo.svg)](https://training.agileops.vn/en/atlassian?hsLang=en) Calculator Estimate licensing costs for Atlassian and Google Workspace ![AgileOps - Calculator](https://resources.agileops.vn/hs-fs/hubfs/raw_assets/public/agileops-theme-v2/images/website-navbar-image/Calculator-nav.png?width=840&height=510&name=Calculator-nav.png) [Atlassian pricing Explore the Atlassian Pricing tool to select the optimal licensing plan for your needs](https://agileops.vn/calculator/atlassian-cloud?hsLang=en) [Google Workspace pricing Concerned about Google Workspace costs? Use the pricing tool to choose the most suitable service package](https://agileops.vn/calculator/google-workspace?hsLang=en) Resources Explore in-depth knowledge, resources and customer stories curated by AgileOps experts ![AgileOps - Resources](https://resources.agileops.vn/hs-fs/hubfs/raw_assets/public/agileops-theme-v2/images/website-navbar-image/Resources-nav.png?width=840&height=510&name=Resources-nav.png) [Blog Stay ahead with updates on Atlassian, HubSpot, Google, and business process optimization](https://resources.agileops.vn/blog?hsLang=en) [Guides & templates Download free guides & templates to elevate business management and project excellence](https://resources.agileops.vn/?hsLang=en) [Customer stories Learn from successful stories of ITSM implementation, process automation, and more](https://resources.agileops.vn/customers?hsLang=en) About Us Explore life at AgileOps and meet our team of experts ![AgileOps - About us](https://resources.agileops.vn/hs-fs/hubfs/raw_assets/public/agileops-theme-v2/images/website-navbar-image/About-us-nav.png?width=840&height=510&name=About-us-nav.png) [Life @ AgileOps Discover the unique work culture at AgileOps as well as explore the dynamic, creative environment of AgileOps-ers](https://agileops.vn/en/life-at-agileops?hsLang=en) [Experts Explore how our expert team can propel your project to success](https://experts.agileops.vn/?hsLang=en) [CONTACT US](https://agileops.vn/en/contact?hsLang=en) Stop misusing Jira issue types - here’s how to get them right ![](https://resources.agileops.vn/hubfs/Team%20profile%20photos/An-Profile.jpg) [Anna Le](https://resources.agileops.vn/en/blog/author/anna-le) 11/06/2025 ![](https://resources.agileops.vn/hubfs/Blogs/BLOG-164/AgileOps%20-%20Jira%20issue%20types%202.png) [![fb-icon](https://resources.agileops.vn/hubfs/raw_assets/public/agileops-theme-v2/icons/Logo%20Facebook.svg)](http://www.facebook.com/share.php?u=https%3A%2F%2Fresources.agileops.vn%2Fen%2Fblog%2Fjira-issue-types%3Futm_medium%3Dsocial%26utm_source%3Dfacebook) [![linkedin-icon](https://resources.agileops.vn/hubfs/raw_assets/public/agileops-theme-v2/icons/Logo%20LinkedIn.svg)](http://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fresources.agileops.vn%2Fen%2Fblog%2Fjira-issue-types%3Futm_medium%3Dsocial%26utm_source%3Dlinkedin) [![twitter-icon](https://resources.agileops.vn/hubfs/raw_assets/public/agileops-theme-v2/icons/Twitter.svg)](https://twitter.com/intent/tweet?original_referer=https%3A%2F%2Fresources.agileops.vn%2Fen%2Fblog%2Fjira-issue-types%3Futm_medium%3Dsocial%26utm_source%3Dtwitter&url=https%3A%2F%2Fresources.agileops.vn%2Fen%2Fblog%2Fjira-issue-types%3Futm_medium%3Dsocial%26utm_source%3Dtwitter&source=tweetbutton&text=) What’s the difference between a Story and a Task in Jira? Should a Bug ever be a Sub-task? And where exactly do Epics fit into the bigger picture? If your team isn’t aligned on how to use Jira issue types, chances are you’re missing out on clean boards, smarter reporting, and faster delivery. This blog unpacks everything you need to know, from the foundational default issue types like stories, tasks, and bugs, to the Jira issue type hierarchy that ties epics and sub-tasks together, plus practical tips to structure these work items for better collaboration and control. ## What are work types in Jira? The anatomy of a Jira work item In Jira, work types, also known as issue types, are essential units that help teams identify, categorize, and manage different pieces of work. Some of the most commonly used issue types in Jira include **Epic**, **Story**, **Task**, **Bug**, and **Sub-task**. Whether you're following Agile, ITIL, or another method of project management, issue types act as blueprints that define how team members interact with work. Using the right structure helps ensure traceability, accountability, and a shared understanding of what’s required to complete each item. Each Jira issue type, whether a task, story, or bug, follows a structured layout that highlights key information. Understanding the design of a Jira standard issue layout helps teams streamline boards, reduce clutter, and focus on what matters most. ![AgileOps - Key components of a Jira work item](https://resources.agileops.vn/hs-fs/hubfs/Blogs/BLOG-164/Blog%20-%20Jira%20issue%20types%2015.png?width=760&height=856&name=Blog%20-%20Jira%20issue%20types%2015.png) *Key components of a Jira work item* 1\. **Description** This is the first section a user sees and should communicate the purpose, scope, and requirements of the unit of work. It’s the ideal place to document user stories, acceptance criteria, or technical requirements. 2\. **Field tabs** If configured, fields can be grouped into different tabs to help separate context for different teams. For instance, developers might need access to one set of fields, while QA teams reference another. 3\. **Context fields** These fields are shown in the Details group and include attributes like assignee, priority, due date, or labels. Each work item can be customized depending on the project or issue type. 4\. **More fields** These are fields that only appear when they contain a value, reducing clutter. If a field doesn’t have a value yet, it remains hidden below the “hide when empty” line, maintaining a clean and focused interface. 5\. **Configure work item layout** Admins can customize the work item layout by choosing which fields appear, where they appear, and under what conditions. This flexibility ensures that the interface adapts to the type of work, the team’s workflow, and the project’s complexity. ## Understanding the Jira issue type hierarchy Jira’s issue type hierarchy is similar to an organizational structure. At the top are high-level goals, which break down into more detailed tasks. This structure helps teams manage scope, progress, and accountability. ![AgileOps - Jira issue type hierarchy](https://resources.agileops.vn/hs-fs/hubfs/Blogs/BLOG-164/The%20Jira%20issue%20type%20hierarchy%202.png?width=760&height=1053&name=The%20Jira%20issue%20type%20hierarchy%202.png) Jira's default issue type hierarchy includes: - Epics: Large bodies of work or strategic goals that can be broken into smaller items; - Standard work items: Tasks, Stories, and Bugs, units of work needed to support an Epic; - Sub-tasks: Detailed child issues tied to parent tasks, stories, or bugs, used to break work into smaller, actionable chunks. Each Jira product comes with these levels by default. Jira admins can customize or extend the hierarchy to fit any method of project management. ## What are parent and child issues? In Jira, the parent and child relationship refers to the hierarchical relationship between work items. - A parent issue is one that contains or is linked to one or more child issues. For example, a task can include multiple sub-tasks. - A child issue is a smaller unit of work that belongs to a parent. For example, a sub-task is always a child of a task, story, or bug. This parent-child structure isn’t restricted to specific issue types, any standard issue type can act as a parent or child, except for sub-tasks, which can only be children since they are at the bottom of the hierarchy. ## The 5 default issue types and when to use each *Jira issue types* ### Epic An Epic represents a significant body of work that may span multiple sprints, teams, or even projects. It's used to group related stories, tasks, and bugs under a single umbrella to track the progress of strategic initiatives or large features. Epics help teams align on high-level goals and provide a roadmap for delivery. They're especially useful in Agile planning when you're trying to connect day-to-day work to long-term objectives. ![Blog - Jira issue types 16.png](https://resources.agileops.vn/hs-fs/hubfs/Blogs/BLOG-164/Blog%20-%20Jira%20issue%20types%2016.png?width=760&height=548&name=Blog%20-%20Jira%20issue%20types%2016.png) *Epic in Jira* In practice, Epics often represent things like launching a new product feature, migrating infrastructure, or completing a compliance requirement. By associating lower-level issues with an Epic, teams can track progress, dependencies, and effort at both a tactical and strategic level. ### Task A Task is a general-purpose issue type used for work that doesn’t fall under specific categories like feature development or bug fixing. Tasks are typically used for operational, technical, or administrative work such as configuration, documentation, refactoring, or internal improvements. Because of its flexibility, the Task issue type acts as a catch-all that supports multiple departments, developers, designers, marketers, and operations alike. For example, IT might use Tasks to track software updates or backups, while marketing may log Tasks for campaign preparation. ### Story A Story describes a specific feature or functionality from the end-user's perspective. Stories are central to Agile workflows, helping teams ensure that each piece of work delivers value to customers or stakeholders. A well-written Story usually follows the user story format: *“As a \[user\], I want \[goal\], so that \[reason\].”* ![AgileOps - Story in Jira](https://resources.agileops.vn/hs-fs/hubfs/Blogs/BLOG-164/Blog%20-%20Jira%20issue%20types%2012.png?width=760&height=548&name=Blog%20-%20Jira%20issue%20types%2012.png) *Story in Jira* Stories help teams break down requirements into digestible, testable, and shippable units of work. For example, building a login page, adding a password reset option, or enabling dark mode would all typically be managed as separate Stories. They can also be estimated using story points, enabling better sprint planning and velocity tracking. ### Sub-task A Sub-task is a smaller, dependent unit of work that’s linked to a parent issue, typically a Task, Story, or Bug. Sub-tasks are used to break down complex work into manageable, assignable actions. They inherit context from the parent issue but allow for finer control of workload distribution, estimation, and progress tracking. For example, if a Story involves building a registration form, Sub-tasks might include creating UI components, integrating API endpoints, writing tests, and updating documentation. This structure helps teams parallelize work, clarify responsibilities, and visualize progress in granular detail. ### Bug A Bug represents a flaw or error in the system that causes unintended behavior, incorrect results, or a degraded user experience. Bugs are usually reported during testing or through user feedback and are critical to maintaining software quality. They often include technical details such as reproduction steps, expected vs. actual results, severity, and affected versions. Jira enables linking bugs to the Stories or Tasks they impact, which helps prioritize fixes and assess scope. For instance, if a Story is considered done but contains unresolved Bugs, it may be flagged during sprint review and pushed back. Prioritizing Bugs ensures faster resolution of blockers and maintains user trust. ## 5 Tips for using Jira issue types effectively ### 1. Standardize issue type usage across teams Consistency is key in a multi-team Jira environment. Define a shared set of standard and custom issue types that reflect your organization’s workflows and ensure every team uses them in the same way. For instance, agree on what qualifies as a Story vs. a Task or when to use Bugs versus Change Requests. This improves cross-project reporting, simplifies filters, and reduces friction during handoffs between teams. ### 2. Use clear naming conventions Jira issue types are only effective if users can instantly understand their purpose. Use descriptive names and consistent formatting, especially when creating custom issue types. For example, instead of vague labels like “Request Type 1,” use terms like “Data Access Request” or “UI Copy Review.” This helps avoid confusion and ensures new team members can onboard faster without second-guessing workflow intent. ### 3. Automate workflows based on issue type Jira’s automation engine lets you tailor actions based on issue types. [Jira automation rules](https://resources.agileops.vn/en/blog/jira-automation-rules?hsLang=en) can significantly reduce manual work and keep your workflows clean and consistent. You can automatically assign Bugs to QA engineers, send email notifications when Change Requests are approved, or trigger Slack alerts. Automation saves time, enforces consistency, and ensures work moves forward without manual intervention. ### 4. Set permissions and controls carefully Only grant admin access or issue type editing permissions to trusted roles. Allowing unrestricted creation of issue types can lead to cluttered workflows and duplicated categories. ![AgileOps - Set permissions](https://resources.agileops.vn/hs-fs/hubfs/Blogs/BLOG-164/Blog%20-%20Jira%20issue%20types%2013.png?width=760&height=548&name=Blog%20-%20Jira%20issue%20types%2013.png) *Set permissions* ### 5. Leverage issue types for smarter dashboards and reporting Properly structured issue types are the foundation of Jira dashboards, filters, and metrics. Use them to create custom burndown charts by story points, monitor bug aging reports, or track epic progress. When each issue type has a defined scope, reporting becomes clearer, helping stakeholders make better decisions and forecast accurately. ## 5 Common mistakes to avoid with Jira issue types ### 1. Creating too many custom issue types One of the most common pitfalls is overusing custom issue types. While Jira supports flexibility, introducing unnecessary or redundant types like “Minor Task,” “Design Task,” and “QA Task” dilutes their meaning and overwhelms users. Instead, use labels, components, or custom fields to differentiate work within a shared issue type. ### 2. Ignoring the issue type hierarchy Jira’s issue type hierarchy (Epic → Story/Task → Sub-task) is there for a reason, it brings structure and traceability. Assigning unrelated subtasks directly under Epics or skipping the hierarchy altogether breaks workflow visibility, affects reporting accuracy, and confuses dependencies. ### 3. Not updating workflows to match new issue types When new issue types are added, they should be paired with relevant workflows. Failing to do this results in issues moving through incorrect or incomplete statuses. ### **4. Using inconsistent issue types across projects** Allowing each project to define its own issue types leads to inconsistencies that block cross-project reporting. For example, if one team uses “Bug” while another uses “Defect,” creating unified reports becomes difficult. Maintaining a global issue type scheme improves governance and scalability. ### 5. Assigning different scopes to the same issue type Treating Bugs as parent-level items in one project and as Sub-tasks in another creates confusion and violates the expected structure. Each issue type should have a clear and consistent level of scope, either atomic (Sub-task), unit of work (Story, Task), or container (Epic), to ensure workflow logic and dependencies remain intact. ## Make Jira work harder for you with the right issue types Jira becomes truly powerful when your team uses issue types intentionally, not just by default. From epics that align with strategic goals to sub-tasks that capture every actionable step, choosing and structuring the right types fuels smarter planning, cleaner execution, and better collaboration. As an [Atlassian Gold Solution Partner](https://agileops.vn/en/services/atlassian?hsLang=en), AgileOps helps high-performing teams optimize their Jira setup, automate processes, and streamline workflows for greater efficiency and control. Ready to unlock the full potential of Jira? Let [AgileOps](https://agileops.vn/en/?hsLang=en) help you configure, automate, and align your Jira workspace for success. [Atlassian](https://resources.agileops.vn/en/blog/tag/atlassian) [Contact us](https://agileops.vn/en/services/atlassian?hsLang=en) Get the latest IT newsletter update ![AgileOps - Cập nhật bản tin IT mới nhất](https://resources.agileops.vn/hubfs/raw_assets/public/agileops-theme-v2/images/thank-you-image.png) Cảm ơn bạn đã gửi thông tin. ## Don't miss out [![AgileOps - Top 15 Confluence templates for dev, IT, and product teams](https://resources.agileops.vn/hubfs/Blogs/BLOG-177/AgileOps%20-%20Confluence%20templates.png)](https://resources.agileops.vn/en/blog/confluence-templates?hsLang=en) [Top 15 Confluence templates for dev, IT, and product teams](https://resources.agileops.vn/en/blog/confluence-templates?hsLang=en) [Your dev team needs a project poster. Marketing’s asking for a product brief. Support wants a runbook yesterday. You’re jumping between tabs, rewriting the same sections, and dealing with mismatched...](https://resources.agileops.vn/en/blog/confluence-templates?hsLang=en) [Anna Le](https://resources.agileops.vn/en/blog/author/anna-le) [Atlassian](https://resources.agileops.vn/en/blog/tag/atlassian) [![AgileOps - Understanding Jira Dashboard](https://resources.agileops.vn/hubfs/Blogs/BLOG-157/AgileOps%20-%20Jira%20Dashboard%201.jpg)](https://resources.agileops.vn/en/blog/jira-dashboard?hsLang=en) [Understanding Jira Dashboard & 8 best practices you need to know](https://resources.agileops.vn/en/blog/jira-dashboard?hsLang=en) [If you’ve ever struggled to keep track of multiple projects, team progress, or blockers in your workflow, a Jira dashboard might be the visual representation your team needs. From software...](https://resources.agileops.vn/en/blog/jira-dashboard?hsLang=en) [Phung Trinh](https://resources.agileops.vn/en/blog/author/phung-trinh) [Atlassian](https://resources.agileops.vn/en/blog/tag/atlassian) [![AgileOps - Choosing Jira plans: Standard, Premium, Enterprise](https://resources.agileops.vn/hubfs/Blogs/BLOG-161/AgileOps%20-%20Jira%20plans%202.png)](https://resources.agileops.vn/en/blog/jira-standard-premium-enterprise?hsLang=en) [Choosing between Jira Standard, Premium, and Enterprise: What you need to know](https://resources.agileops.vn/en/blog/jira-standard-premium-enterprise?hsLang=en) [Atlassian offers Jira Cloud in four distinct plans: Free, Standard, Premium, and Enterprise. Each plan is designed to support different levels of team size, complexity, and operational scale. This...](https://resources.agileops.vn/en/blog/jira-standard-premium-enterprise?hsLang=en) [Phung Trinh](https://resources.agileops.vn/en/blog/author/phung-trinh) [Atlassian](https://resources.agileops.vn/en/blog/tag/atlassian) [![AgileOps - Dynamically defining approver field the Jira automation way](https://resources.agileops.vn/hubfs/Blogs/BLOG-33/image%20(7).png)](https://resources.agileops.vn/en/blog/defining-approver-field-jira-automation?hsLang=en) [Dynamically defining approver field the Jira automation way](https://resources.agileops.vn/en/blog/defining-approver-field-jira-automation?hsLang=en) [Choosing the right approvers for requests is an important part of effective and smooth workflow management in organizations. The appropriate individuals or teams can review and approve requests,...](https://resources.agileops.vn/en/blog/defining-approver-field-jira-automation?hsLang=en) [Kiet Ngo](https://resources.agileops.vn/en/blog/author/kiet-ngo) [Atlassian](https://resources.agileops.vn/en/blog/tag/atlassian) [ITSM & ESM](https://resources.agileops.vn/en/blog/tag/itsm-esm) [![AgileOps - Jira vs ClickUp: Feature-by-feature breakdown for modern teams](https://resources.agileops.vn/hubfs/AgileOps%20-%20Jira%20vs%20clickup.png)](https://resources.agileops.vn/en/blog/jira-vs-clickup?hsLang=en) [Jira vs ClickUp: Feature-by-feature breakdown for modern teams](https://resources.agileops.vn/en/blog/jira-vs-clickup?hsLang=en) [What happens when your team outgrows sticky notes and spreadsheets? You look for a project management tool that actually works. That’s when two big names pop up: Jira and ClickUp. Your engineering...](https://resources.agileops.vn/en/blog/jira-vs-clickup?hsLang=en) [Anna Le](https://resources.agileops.vn/en/blog/author/anna-le) [Atlassian](https://resources.agileops.vn/en/blog/tag/atlassian) [Product Comparison](https://resources.agileops.vn/en/blog/tag/product-comparison) [![AgileOps - How AgileOps built a mini-CRM with Jira Service Management?](https://resources.agileops.vn/hubfs/Blogs/BLOG-159/AgileOps%20-%20Implement%20a%20mini-CRM%20with%20Jira%20Service%20Management.png)](https://resources.agileops.vn/en/blog/mini-crm-with-jira-service-management?hsLang=en) [How AgileOps built a mini-CRM with Jira Service Management](https://resources.agileops.vn/en/blog/mini-crm-with-jira-service-management?hsLang=en) [Imagine using Jira Service Management (JSM) not just for IT operations, but as a robust CRM solution tailored to your business needs. At AgileOps, we've transformed JSM into a powerful mini CRM,...](https://resources.agileops.vn/en/blog/mini-crm-with-jira-service-management?hsLang=en) [Kiet Ngo](https://resources.agileops.vn/en/blog/author/kiet-ngo) [Atlassian](https://resources.agileops.vn/en/blog/tag/atlassian) [Business](https://resources.agileops.vn/en/blog/tag/business) [![Footer - Logo](https://resources.agileops.vn/hubfs/raw_assets/public/agileops-theme-v2/images/website-home-image/AgileOps-Footer.svg)](https://agileops.vn/?hsLang=en) [![Logo Upwork](https://resources.agileops.vn/hubfs/raw_assets/public/agileops-theme-v2/icons/Logo%20Upwork.svg)](https://www.upwork.com/agencies/agileops/) [![Logo LinkedIn](https://resources.agileops.vn/hubfs/raw_assets/public/agileops-theme-v2/icons/Logo%20LinkedIn.svg)](https://www.linkedin.com/company/agileopsvn) [![Logo Facebook](https://resources.agileops.vn/hubfs/raw_assets/public/agileops-theme-v2/icons/Logo-Facebook.svg)](https://www.facebook.com/agileops) ![atlassian-footer](https://resources.agileops.vn/hubfs/website/partner%20badge/atlassian-footer.svg) Tầng 9, tòa nhà Flemington 182 Lê Đại Hành, P. Phú Thọ, Thành phố Hồ Chí Minh [028 22222722](tel:02822222722) - [028 22222522](tel:02822222522) Services [Atlassian](https://agileops.vn/en/services/atlassian?hsLang=en) [HubSpot](https://agileops.vn/en/services/hubspot?hsLang=en) [Google](https://agileops.vn/en/services/google-workspace?hsLang=en) [Kubernetes](https://agileops.vn/en/services/kubernetes?hsLang=en) [Salesforce](https://agileops.vn/en/services/salesforce?hsLang=en) Calculator [Atlassian pricing](https://agileops.vn/calculator/atlassian-cloud?hsLang=en) [Google Workspace pricing](https://agileops.vn/calculator/google-workspace?hsLang=en) Resources [Blog](https://resources.agileops.vn/blog?hsLang=en) [Guides & templates](https://resources.agileops.vn?hsLang=en) [Customer stories](https://resources.agileops.vn/customers?hsLang=en) About Us [Life @ AgileOps](https://agileops.vn/en/life-at-agileops?hsLang=en) [Experts](https://experts.agileops.vn?hsLang=en) [Liên hệ Bạn cần hỗ trợ? Chúng tôi nhanh chóng giải quyết vấn đề của bạn.](https://agileops.vn/en/contact?hsLang=en) Tầng 9, tòa nhà Flemington 182 Lê Đại Hành, P. Phú Thọ, , Thành phố Hồ Chí Minh [028 22222722](tel:02822222722) - [028 22222522](tel:02822222522) [![Logo Upwork](https://resources.agileops.vn/hubfs/raw_assets/public/agileops-theme-v2/icons/Logo%20Upwork.svg)](https://www.upwork.com/agencies/agileops/) [![Logo LinkedIn](https://resources.agileops.vn/hubfs/raw_assets/public/agileops-theme-v2/icons/Logo%20LinkedIn.svg)](https://www.linkedin.com/company/agileopsvn) [![Logo Facebook](https://resources.agileops.vn/hubfs/raw_assets/public/agileops-theme-v2/icons/Logo-Facebook.svg)](https://www.facebook.com/agileops) © 2022 AGILEOPS, ALL RIGHTS RESERVED | [Privacy Policy](https://agileops.vn/privacy-policy?hsLang=en) | [Legals](https://agileops.vn/legal?hsLang=en) ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Anna Le", "url" : "https://resources.agileops.vn/en/blog/author/anna-le" }, "dateModified" : "2025-06-11T03:38:04.709Z", "datePublished" : "2025-06-11T03:38:04.000Z", "headline" : "Stop misusing Jira issue types - here’s how to get them right", "image" : [ "https://resources.agileops.vn/hubfs/Blogs/BLOG-164/AgileOps%20-%20Jira%20issue%20types%202.png" ], "mainEntityOfPage" : { "@id" : "https://resources.agileops.vn/en/blog/jira-issue-types", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://resources.agileops.vn/hubfs/1200x1200%20v%C3%A0ng.svg" }, "name" : "AgileOps" } } ``` ```json { "@context" : "https://schema.org", "@type" : "VideoObject", "caption" : { "@type" : "MediaObject", "contentUrl" : "https://resources.agileops.vn/media-transcripts/190623812919/en.vtt", "inLanguage" : "en", "name" : "en Captions" }, "contentUrl" : "https://24400165.fs1.hubspotusercontent-na2.net/hubfs/24400165/Blogs/BLOG-159/Atlassian_CRM_4_mins_S30.mp4", "dateModified" : "2025-10-30T05:38:37.156Z", "duration" : "PT3M54S", "height" : 1080, "name" : "Atlassian_CRM_4_mins_S30", "thumbnailUrl" : "https://24400165.fs1.hubspotusercontent-na2.net/hubfs/24400165/Blogs/BLOG-159/Atlassian_CRM_4_mins_S30.mp4/medium.jpg", "uploadDate" : "2025-05-26T08:02:59.886Z", "width" : 2192 } ```