{"id":9666,"date":"2021-05-24T21:23:23","date_gmt":"2021-05-24T15:53:23","guid":{"rendered":"https:\/\/www.h2kinfosys.com\/blog\/?p=9666"},"modified":"2026-01-08T02:27:52","modified_gmt":"2026-01-08T07:27:52","slug":"jira-issues-and-types","status":"publish","type":"post","link":"https:\/\/www.h2kinfosys.com\/blog\/jira-issues-and-types\/","title":{"rendered":"JIRA &#8211; Issues and Types"},"content":{"rendered":"\n<p>In today\u2019s fast-paced software development world, tools like <strong>JIRA<\/strong> have become indispensable. Whether you\u2019re managing a small agile project or handling enterprise-level workflows, JIRA helps teams track, organize, and resolve issues efficiently. For anyone pursuing <strong><a href=\"https:\/\/www.h2kinfosys.com\/courses\/qa-online-training-course-details\/\">QA tester training<\/a><\/strong> or exploring professional <strong>testing courses<\/strong>, understanding JIRA and its issue types is a must.<\/p>\n\n\n\n<p>This comprehensive guide explains what JIRA is, the types of issues it manages, and how QA testers use it daily to ensure seamless testing cycles and quality assurance.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>1. What is JIRA?<\/strong><\/h2>\n\n\n\n<figure class=\"wp-block-image size-full is-resized\"><img fetchpriority=\"high\" decoding=\"async\" width=\"341\" height=\"148\" src=\"https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2021\/05\/image-7.png\" alt=\"\" class=\"wp-image-31905\" style=\"width:840px;height:auto\" title=\"\" srcset=\"https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2021\/05\/image-7.png 341w, https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2021\/05\/image-7-300x130.png 300w, https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2021\/05\/image-7-150x65.png 150w\" sizes=\"(max-width: 341px) 100vw, 341px\" \/><\/figure>\n\n\n\n<p>JIRA is a <strong>project management and issue tracking tool<\/strong> developed by <strong>Atlassian<\/strong>. Initially designed for bug tracking, it has evolved into a versatile platform supporting <strong>agile development<\/strong>, <strong>scrum boards<\/strong>, <strong>kanban boards<\/strong>, and <strong>software testing workflows<\/strong>.<\/p>\n\n\n\n<p>In essence, JIRA allows teams to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Create and manage issues (tasks, bugs, stories, etc.)<\/li>\n\n\n\n<li>Plan sprints and track progress<\/li>\n\n\n\n<li>Collaborate across teams<\/li>\n\n\n\n<li>Integrate with CI\/CD tools and testing frameworks<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Why QA Testers Use<\/strong><\/h3>\n\n\n\n<p>For QA professionals, JIRA acts as a <strong>central hub<\/strong> for tracking test cases, reporting bugs, and collaborating with developers. It provides complete visibility into every defect\u2019s life cycle, from discovery to resolution.<\/p>\n\n\n\n<p><strong>Key benefits for QA testers:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Easy bug reporting with screenshots and attachments<\/li>\n\n\n\n<li>Real-time updates on issue status<\/li>\n\n\n\n<li>Integration with automation tools (like Selenium or Jenkins)<\/li>\n\n\n\n<li>Custom dashboards for testing metrics<\/li>\n<\/ul>\n\n\n\n<p>When you enroll in a <strong>QA tester training program<\/strong>, you\u2019ll often find JIRA among the top tools covered in the curriculum \u2014 and for good reason.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>2. Understanding Issues<\/strong><\/h2>\n\n\n\n<p>In JIRA, <strong>everything revolves around an issue<\/strong>. An issue is a record that tracks a piece of work such as a bug, task, improvement, or story. Each issue holds essential details, including:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Summary and description<\/li>\n\n\n\n<li>Assignee and reporter<\/li>\n\n\n\n<li>Priority and status<\/li>\n\n\n\n<li>Attachments, comments, and logs<\/li>\n<\/ul>\n\n\n\n<p>Think of issues as the <strong>core building blocks<\/strong> of JIRA. Developers, testers, and project managers all rely on them to communicate progress and responsibilities.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>3. Issue Hierarchy<\/strong><\/h2>\n\n\n\n<p>Before diving into issue types, it\u2019s crucial to understand how issues are organized in JIRA. The hierarchy typically follows this structure:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Epic<\/strong> \u2013 A large body of work that can be broken into multiple stories or tasks.<\/li>\n\n\n\n<li><strong>Story<\/strong> \u2013 A user requirement or functionality.<\/li>\n\n\n\n<li><strong>Task<\/strong> \u2013 A specific piece of work that contributes to the story.<\/li>\n\n\n\n<li><strong>Sub-task<\/strong> \u2013 A smaller, detailed activity within a task or story.<\/li>\n\n\n\n<li><strong>Bug<\/strong> \u2013 An error, flaw, or defect identified during testing.<\/li>\n<\/ol>\n\n\n\n<p>This hierarchy helps teams organize their workload, from big-picture features down to minor bug fixes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>4. Common Issue Types<\/strong><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>a. Bug<\/strong><\/h3>\n\n\n\n<p>A <strong>bug<\/strong> represents an error or defect discovered in the application during testing.<br><strong>Example:<\/strong> A login button doesn\u2019t work after a new deployment.<\/p>\n\n\n\n<p><strong>Key attributes of a bug:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Status:<\/strong> Open \u2192 In Progress \u2192 Resolved \u2192 Closed<\/li>\n\n\n\n<li><strong>Priority levels:<\/strong> Blocker, Critical, Major, Minor, Trivial<\/li>\n\n\n\n<li><strong>Reporter:<\/strong> Usually a QA tester<\/li>\n\n\n\n<li><strong>Assignee:<\/strong> Developer responsible for fixing the issue<\/li>\n<\/ul>\n\n\n\n<p>In any <strong>QA tester training<\/strong>, reporting bugs correctly is emphasized including reproducing steps, environment details, and screenshots.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>b. Story<\/strong><\/h3>\n\n\n\n<p>A <strong>story<\/strong> (or user story) represents a feature or requirement from the end user\u2019s perspective.<br><strong>Example:<\/strong> \u201cAs a user, I want to reset my password so that I can regain account access.\u201d<\/p>\n\n\n\n<p>Stories are typically used in <strong>Agile<\/strong> and <strong>Scrum<\/strong> projects to capture business requirements. QA testers create test cases based on these stories and verify that the functionality meets acceptance criteria.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>c. Task<\/strong><\/h3>\n\n\n\n<p>A <strong>task<\/strong> refers to general work that needs to be completed not necessarily linked to a defect or user story.<br><strong>Example:<\/strong> \u201cUpdate the test environment configuration.\u201d<\/p>\n\n\n\n<p>Tasks are ideal for administrative or support activities, such as test data preparation or environment setup.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>d. Sub-task<\/strong><\/h3>\n\n\n\n<p>A <strong>sub-task<\/strong> breaks down a larger issue (like a story or task) into smaller, actionable steps.<br><strong>Example:<\/strong> Under a story \u201cImplement user registration,\u201d sub-tasks could be:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Design UI for registration page<\/li>\n\n\n\n<li>Write validation scripts<\/li>\n\n\n\n<li>Test API endpoints<\/li>\n<\/ul>\n\n\n\n<p>Sub-tasks make complex work easier to manage and assign to multiple team members.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>e. Epic<\/strong><\/h3>\n\n\n\n<p>An <strong>Epic<\/strong> is a collection of related stories that represent a significant deliverable or project goal.<br><strong>Example:<\/strong> \u201cUser Management Module\u201d may include multiple stories like login, registration, and password reset.<\/p>\n\n\n\n<p>Epics help QA teams plan testing at a <strong>macro level<\/strong> tracking all related test cases, automation scripts, and bug reports under one large initiative.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>f. Improvement<\/strong><\/h3>\n\n\n\n<p>An <strong>improvement<\/strong> represents an enhancement or optimization to an existing feature.<br><strong>Example:<\/strong> \u201cImprove search speed on the dashboard page.\u201d<\/p>\n\n\n\n<p>While not necessarily a bug, these issues are crucial for continuous enhancement of software quality.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>5. Additional Custom Issue Types<\/strong><\/h2>\n\n\n\n<p>It is highly customizable. Depending on the organization\u2019s workflow, administrators can define <strong>custom issue types<\/strong> such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Change Request<\/strong><\/li>\n\n\n\n<li><strong>Test Case<\/strong><\/li>\n\n\n\n<li><strong>Incident<\/strong><\/li>\n\n\n\n<li><strong>Technical Debt<\/strong><\/li>\n<\/ul>\n\n\n\n<p>For instance, in QA-focused projects, many teams create a <strong>Test Case<\/strong> issue type to manage manual or automated test scenarios directly in JIRA.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>6. JIRA Issue Fields Explained<\/strong><\/h2>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"735\" height=\"803\" src=\"https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2021\/05\/image-8.png\" alt=\"\" class=\"wp-image-31906\" title=\"\" srcset=\"https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2021\/05\/image-8.png 735w, https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2021\/05\/image-8-275x300.png 275w, https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2021\/05\/image-8-150x164.png 150w\" sizes=\"(max-width: 735px) 100vw, 735px\" \/><\/figure>\n\n\n\n<p>Each issue type in JIRA comes with customizable fields that provide detailed information. Common fields include:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>Field Name<\/strong><\/th><th><strong>Purpose<\/strong><\/th><\/tr><\/thead><tbody><tr><td><strong>Summary<\/strong><\/td><td>A short title for the issue<\/td><\/tr><tr><td><strong>Description<\/strong><\/td><td>Detailed explanation of the issue<\/td><\/tr><tr><td><strong>Assignee<\/strong><\/td><td>Person responsible for resolving it<\/td><\/tr><tr><td><strong>Reporter<\/strong><\/td><td>Person who identified the issue<\/td><\/tr><tr><td><strong>Priority<\/strong><\/td><td>Importance level (Critical, Major, etc.)<\/td><\/tr><tr><td><strong>Status<\/strong><\/td><td>Current progress (Open, In Progress, Done)<\/td><\/tr><tr><td><strong>Labels<\/strong><\/td><td>Tags for easy search and categorization<\/td><\/tr><tr><td><strong>Comments<\/strong><\/td><td>Notes or updates from team members<\/td><\/tr><tr><td><strong>Attachments<\/strong><\/td><td>Screenshots, logs, or related files<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Understanding these fields is an essential skill you\u2019ll gain during <strong>QA tester training<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>7. Issue Workflo<\/strong>w<\/h2>\n\n\n\n<p>Every issue in JIRA follows a <strong>workflow<\/strong>, representing its journey from creation to closure. Workflows can be customized but typically include these stages:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Open \/ To Do:<\/strong> The issue has been created and awaits action.<\/li>\n\n\n\n<li><strong>In Progress:<\/strong> Assigned team members are working on it.<\/li>\n\n\n\n<li><strong>In Review \/ Testing:<\/strong> QA verifies if the issue is resolved.<\/li>\n\n\n\n<li><strong>Resolved \/ Done:<\/strong> The issue has been fixed or completed.<\/li>\n\n\n\n<li><strong>Closed:<\/strong> Final verification confirms it\u2019s ready for release.<\/li>\n<\/ol>\n\n\n\n<p>Workflows help QA testers ensure <strong>traceability<\/strong> and maintain accountability throughout the testing life cycle.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>8. How QA Testers Use JIRA in the Real World<\/strong><\/h2>\n\n\n\n<p>serves as a critical part of the <strong>software testing process<\/strong>. Here\u2019s how QA testers typically use it:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>1. Defect Logging<\/strong><\/h3>\n\n\n\n<p>When testers find a bug, they create a <strong>Bug issue<\/strong> in JIRA, describing:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Steps to reproduce<\/li>\n\n\n\n<li>Expected vs. actual results<\/li>\n\n\n\n<li>Severity and priority<\/li>\n\n\n\n<li>Supporting screenshots or videos<\/li>\n<\/ul>\n\n\n\n<p>This structured approach ensures developers can easily reproduce and fix the issue.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>2. Test Cycle Management<\/strong><\/h3>\n\n\n\n<p>In integrated setups (like <strong>JIRA + Zephyr<\/strong> or <strong>JIRA + Xray<\/strong>), testers manage their entire <strong>test cycle<\/strong> from planning to execution within JIRA itself.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>3. Traceability Matrix<\/strong><\/h3>\n\n\n\n<p>By linking <strong>user stories<\/strong>, <strong>test cases<\/strong>, and <strong>bugs<\/strong>, QA teams ensure all requirements are tested and no defect is overlooked.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>4. Collaboration<\/strong><\/h3>\n\n\n\n<p>JIRA enhances cross-functional communication. Developers, testers, and business analysts can all comment, tag, and track progress within the same platform.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>5. Reporting and Dashboards<\/strong><\/h3>\n\n\n\n<p>JIRA\u2019s dashboard and report features give QA managers insights into:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Number of open\/closed bugs<\/li>\n\n\n\n<li>Sprint progress<\/li>\n\n\n\n<li>Testing velocity<\/li>\n\n\n\n<li>Team performance<\/li>\n<\/ul>\n\n\n\n<p>During <strong>testing courses<\/strong>, learners are often taught how to use these analytics features to evaluate QA efficiency.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>9. Integration with Testing Tools<\/strong><\/h2>\n\n\n\n<p>JIRA\u2019s power multiplies when integrated with other tools in the <strong>QA ecosystem<\/strong>:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Selenium:<\/strong> Automates regression tests and links results to JIRA tickets.<\/li>\n\n\n\n<li><strong>Jenkins:<\/strong> Automates build and deployment processes tied to JIRA issues.<\/li>\n\n\n\n<li><strong>Zephyr \/ Xray:<\/strong> Manage test cases and execution results inside JIRA.<\/li>\n\n\n\n<li><strong>Confluence:<\/strong> Stores documentation related to JIRA issues.<\/li>\n<\/ul>\n\n\n\n<p>Learning how to integrate these tools is a major component of modern <strong>QA tester training<\/strong> programs.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>10. Best Practices for Managing JIRA Issues<\/strong><\/h2>\n\n\n\n<p>Here are some proven tips QA testers can follow to maintain clarity and consistency in <a href=\"https:\/\/www.h2kinfosys.com\/blog\/tag\/jira\/\" data-type=\"post_tag\" data-id=\"591\">JIRA<\/a>:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Use clear, concise titles<\/strong> \u2013 e.g., \u201cLogin page crashes on invalid input.\u201d<\/li>\n\n\n\n<li><strong>Attach evidence<\/strong> \u2013 screenshots, logs, or screen recordings.<\/li>\n\n\n\n<li><strong>Set correct priority levels<\/strong> \u2013 avoid marking everything as \u201cCritical.\u201d<\/li>\n\n\n\n<li><strong>Update issue statuses regularly<\/strong> \u2013 ensures transparency across teams.<\/li>\n\n\n\n<li><strong>Use labels and components<\/strong> \u2013 makes searching and filtering easier.<\/li>\n\n\n\n<li><strong>Add acceptance criteria<\/strong> \u2013 defines when an issue is considered done.<\/li>\n\n\n\n<li><strong>Collaborate via comments<\/strong> \u2013 document all key communications.<\/li>\n<\/ol>\n\n\n\n<p>By mastering these habits, QA testers enhance productivity and reduce communication gaps between testing and development teams.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>11. Common Challenges and How to Overcome Them<\/strong><\/h2>\n\n\n\n<p>While JIRA is robust, beginners might face some challenges:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>Challenge<\/strong><\/th><th><strong>Solution<\/strong><\/th><\/tr><\/thead><tbody><tr><td>Complex navigation for new users<\/td><td>Take hands-on practice through QA tester training labs<\/td><\/tr><tr><td>Overwhelming number of issue types<\/td><td>Start with core ones: Bug, Task, Story<\/td><\/tr><tr><td>Miscommunication between QA and Dev<\/td><td>Use clear descriptions and tagging<\/td><\/tr><tr><td>Workflow confusion<\/td><td>Customize or simplify workflow diagrams<\/td><\/tr><tr><td>Duplicate issues<\/td><td>Use advanced search (JQL) before creating new tickets<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>Many <strong>testing courses<\/strong> include JIRA labs and real-time project assignments to help students overcome these challenges quickly.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>12.Query Language (JQL): A QA Tester\u2019s Secret Weapon<\/strong><\/h2>\n\n\n\n<p>Advanced testers often use <strong>JQL (JIRA Query Language)<\/strong> to filter and find issues efficiently.<br>Examples:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">project = \"Banking App\" AND issuetype = Bug AND status != Closed\n<\/pre>\n\n\n\n<p>This query retrieves all open bugs in the \u201cBanking App\u201d project.<\/p>\n\n\n\n<p>Learning JQL can drastically improve your testing productivity and is a skill highly valued in QA interviews.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>13. Learning JIRA Through QA Tester Training<\/strong><\/h2>\n\n\n\n<p>Most professional <strong>QA tester training programs<\/strong> include JIRA as part of their syllabus. Students learn:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>How to report and track bugs<\/li>\n\n\n\n<li>How to manage Agile boards<\/li>\n\n\n\n<li>How to create dashboards and metrics<\/li>\n\n\n\n<li>How to integrate JIRA with automation tools<\/li>\n<\/ul>\n\n\n\n<p>By practicing real-world scenarios, learners gain job-ready experience that translates directly to the workplace.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>14. Why Understanding JIRA Matters for QA Careers<\/strong><\/h2>\n\n\n\n<p>Mastering JIRA can significantly boost your career opportunities. Recruiters often prefer QA candidates proficient in:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/en.wikipedia.org\/wiki\/Bug_tracking_system\" rel=\"nofollow noopener\" target=\"_blank\">Bug and issue tracking<\/a><\/li>\n\n\n\n<li>Agile sprint management<\/li>\n\n\n\n<li>Collaboration and documentation tools<\/li>\n<\/ul>\n\n\n\n<p>JIRA skills demonstrate that you can work efficiently within modern software teams and handle dynamic project workflows essential for roles like <strong>QA Analyst<\/strong>, <strong>Test Engineer<\/strong>, or <strong>Agile Tester<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Conclusion<\/strong><\/h2>\n\n\n\n<p>It is more than just an issue tracker  it\u2019s a <strong>powerful collaboration and quality management tool<\/strong> at the heart of modern QA workflows. From identifying defects to tracking user stories and managing test cycles, JIRA gives teams the structure and transparency needed for successful releases.<\/p>\n\n\n\n<p>For aspiring QA professionals, mastering should be a top priority. Whether you\u2019re new to testing or advancing your career through <strong>QA tester training<\/strong> or other <strong><a href=\"https:\/\/www.h2kinfosys.com\/courses\/qa-online-training-course-details\/\">Testing courses<\/a><\/strong>, gaining hands-on JIRA experience will give you a competitive edge in the job market.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In today\u2019s fast-paced software development world, tools like JIRA have become indispensable. Whether you\u2019re managing a small agile project or handling enterprise-level workflows, JIRA helps teams track, organize, and resolve issues efficiently. For anyone pursuing QA tester training or exploring professional testing courses, understanding JIRA and its issue types is a must. This comprehensive guide [&hellip;]<\/p>\n","protected":false},"author":20,"featured_media":9669,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[],"class_list":["post-9666","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-qa-tutorials"],"_links":{"self":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/9666","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/users\/20"}],"replies":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/comments?post=9666"}],"version-history":[{"count":3,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/9666\/revisions"}],"predecessor-version":[{"id":31915,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/9666\/revisions\/31915"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/media\/9669"}],"wp:attachment":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/media?parent=9666"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/categories?post=9666"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/tags?post=9666"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}