{"id":6155,"date":"2026-01-16T05:59:29","date_gmt":"2026-01-16T10:59:29","guid":{"rendered":"https:\/\/www.h2kinfosys.com\/blog\/?p=6155"},"modified":"2026-01-26T02:09:21","modified_gmt":"2026-01-26T07:09:21","slug":"how-to-use-jira","status":"publish","type":"post","link":"https:\/\/www.h2kinfosys.com\/blog\/how-to-use-jira\/","title":{"rendered":"How to use JIRA?"},"content":{"rendered":"\n<p>In the world of <strong><a href=\"https:\/\/www.h2kinfosys.com\/courses\/qa-online-training-course-details\/\">Software testing and quality assurance<\/a><\/strong>, efficiency, traceability, and transparency are everything. One tool that stands out as a game-changer in this space is <strong>JIRA<\/strong>, a robust project management and bug-tracking solution developed by Atlassian. Whether you\u2019re a QA engineer, project manager, or a student enrolled in <strong>Quality assurance software testing courses<\/strong>, learning how to use JIRA can help you organize, monitor, and optimize every stage of your testing lifecycle.<\/p>\n\n\n\n<p>This guide breaks down the essentials of using JIRA from setup to workflow customization and demonstrates how mastering this platform can enhance your productivity and collaboration in software testing.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>1. What Is JIRA and Why Is It Important in QA?<\/strong><\/h2>\n\n\n\n<p><strong>JIRA<\/strong> is primarily a project tracking and issue management tool widely used in <strong>Agile<\/strong>, <strong>Scrum<\/strong>, and <strong>Kanban<\/strong> environments. While originally built for software development teams, it has evolved into a flexible tool for tracking tasks, bugs, sprints, and test cycles.<\/p>\n\n\n\n<p>For QA professionals, JIRA serves as a single source of truth enabling testers to log defects, assign tasks, track progress, and ensure alignment with the development team. It\u2019s also a critical part of modern <strong>Software testing and quality assurance courses<\/strong>, where students learn to manage software projects and ensure quality control through real-world tools.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Key Benefits of Using JIRA in QA<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Centralized defect tracking and resolution<\/li>\n\n\n\n<li>Seamless integration with automation and CI\/CD tools<\/li>\n\n\n\n<li>Real-time visibility into project progress<\/li>\n\n\n\n<li>Detailed reporting and analytics for test coverage<\/li>\n\n\n\n<li>Supports Agile frameworks like Scrum and Kanban<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>2. Getting Started with JIRA<\/strong><\/h2>\n\n\n\n<p>Before diving into test case creation and tracking, you\u2019ll need to set up JIRA for your project.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img fetchpriority=\"high\" decoding=\"async\" width=\"1024\" height=\"337\" src=\"https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2020\/10\/image-7-1024x337.png\" alt=\"\" class=\"wp-image-31382\" title=\"\" srcset=\"https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2020\/10\/image-7-1024x337.png 1024w, https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2020\/10\/image-7-300x99.png 300w, https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2020\/10\/image-7-768x252.png 768w, https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2020\/10\/image-7.png 1065w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 1: Sign Up and Log In<\/strong><\/h3>\n\n\n\n<p>Visit Atlassian JIRA and create an account. You can choose <strong><a href=\"https:\/\/www.h2kinfosys.com\/blog\/jira-software-essentials-associate-certification\/\" data-type=\"post\" data-id=\"19128\">JIRA Software<\/a><\/strong>, <strong>JIRA Service Management<\/strong>, or <strong>JIRA Work Management<\/strong>. For QA purposes, <strong>JIRA Software<\/strong> is ideal. Once registered, you can either join an existing project or create a new one.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 2: Create a New Project<\/strong><\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Click <strong>Projects \u2192 Create Project<\/strong><\/li>\n\n\n\n<li>Choose a <strong>template<\/strong> (Scrum, Kanban, or Bug Tracking)<\/li>\n\n\n\n<li>Name your project and define a <strong>key<\/strong> (e.g., QA2025)<\/li>\n\n\n\n<li>Set up permissions and roles for your team members<\/li>\n<\/ol>\n\n\n\n<p>For <strong>Quality assurance software testing courses<\/strong>, instructors often recommend starting with a <strong>Scrum template<\/strong>, as it helps students understand sprints and iterative testing.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>3. Understanding JIRA Interface and Key Components<\/strong><\/h2>\n\n\n\n<p>Once inside your project, you\u2019ll notice that JIRA revolves around three key elements:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Issues<\/strong><\/h3>\n\n\n\n<p>An <strong>Issue<\/strong> in JIRA can represent anything a task, bug, story, or epic. In QA workflows, issues typically represent <strong>test cases<\/strong>, <strong>defects<\/strong>, or <strong>requirements<\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Boards<\/strong><\/h3>\n\n\n\n<p>Boards visualize the workflow. You can choose:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Scrum boards<\/strong> for sprint-based workflows<\/li>\n\n\n\n<li><strong>Kanban boards<\/strong> for continuous testing and monitoring<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Backlog<\/strong><\/h3>\n\n\n\n<p>The <strong>backlog<\/strong> stores all tasks that are yet to be worked on. QA teams use it to maintain a list of pending test cases or defects awaiting prioritization.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Filters and Dashboards<\/strong><\/h3>\n\n\n\n<p>Filters help you find specific issues quickly (e.g., \u201cOpen Bugs assigned to QA\u201d).<br>Dashboards display real-time project metrics, perfect for team meetings or project tracking.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>4. Creating and Managing Issues<\/strong><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 1: Create an Issue<\/strong><\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Click <strong>Create \u2192 Issue<\/strong><\/li>\n\n\n\n<li>Choose issue type: <em>Bug, Task, Story, or Epic<\/em><\/li>\n\n\n\n<li>Add a <strong>summary<\/strong>, <strong>description<\/strong>, and <strong>priority<\/strong> level<\/li>\n\n\n\n<li>Assign it to a team member<\/li>\n\n\n\n<li>Attach screenshots or logs for clarity<\/li>\n<\/ol>\n\n\n\n<p>For QA testers, a <strong>Bug<\/strong> issue type is most commonly used. Detailed descriptions and attachments help developers reproduce the issue easily.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Step 2: Workflow Management<\/strong><\/h3>\n\n\n\n<p>Each issue goes through a workflow from <strong>Open \u2192 In Progress \u2192 In Review \u2192 Done<\/strong>.<br>You can customize this workflow to suit your QA process. For instance:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u201cTo Do\u201d \u2192 \u201cIn Testing\u201d \u2192 \u201cBlocked\u201d \u2192 \u201cResolved\u201d \u2192 \u201cClosed\u201d<\/li>\n<\/ul>\n\n\n\n<p>This flexibility makes JIRA invaluable for teams enrolled in a <strong>Software testing and quality assurance course<\/strong>, as it mirrors real-world software lifecycle practices.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>5. Tracking Bugs and Defects in JIRA<\/strong><\/h2>\n\n\n\n<p>Bug tracking is the backbone of quality assurance. JIRA\u2019s robust issue-tracking <a href=\"https:\/\/en.wikipedia.org\/wiki\/Capability_approach\" rel=\"nofollow noopener\" target=\"_blank\">capability makes<\/a> it easy to manage defects from discovery to closure.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Steps for Bug Tracking<\/strong><\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Create a new issue and select <strong>Bug<\/strong> as the issue type.<\/li>\n\n\n\n<li>Fill in key fields:\n<ul class=\"wp-block-list\">\n<li><strong>Summary:<\/strong> \u201cLogin button not responsive on Chrome\u201d<\/li>\n\n\n\n<li><strong>Description:<\/strong> Steps to reproduce the issue<\/li>\n\n\n\n<li><strong>Priority:<\/strong> Critical, Major, or Minor<\/li>\n\n\n\n<li><strong>Environment:<\/strong> Browser, OS, or device info<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Assign it to a developer<\/li>\n\n\n\n<li>Add comments or attachments (like screenshots or logs)<\/li>\n<\/ol>\n\n\n\n<p>Once the developer fixes the bug, it\u2019s sent back to QA for verification. The tester then changes the status to <strong>Closed<\/strong> once confirmed<\/p>\n\n\n\n<p>This structured approach is what many <strong>Quality assurance software testing courses<\/strong> emphasize ensuring every bug is documented, tracked, and resolved efficiently.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>6. Customizing Workflows in JIRA<\/strong><\/h2>\n\n\n\n<p>A major strength of JIRA is its customizable workflow engine. Each organization or project may have its unique testing process, and JIRA adapts to it easily.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Steps to Customize Workflows<\/strong><\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Navigate to <strong>Project Settings \u2192 Workflows<\/strong><\/li>\n\n\n\n<li>Click <strong>Edit Workflow<\/strong><\/li>\n\n\n\n<li>Add or rename statuses (e.g., \u201cReady for Testing,\u201d \u201cBlocked\u201d)<\/li>\n\n\n\n<li>Define transitions (e.g., from \u201cOpen\u201d to \u201cIn Testing\u201d)<\/li>\n\n\n\n<li>Save and publish the workflow<\/li>\n<\/ol>\n\n\n\n<p>You can even create <strong>custom fields<\/strong> to capture specific QA information such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Test environment<\/li>\n\n\n\n<li>Root cause analysis<\/li>\n\n\n\n<li>Test case ID<\/li>\n\n\n\n<li>Automation status<\/li>\n<\/ul>\n\n\n\n<p>In <strong>Software testing and quality assurance courses<\/strong>, learning how to modify workflows teaches students to build test processes tailored to organizational needs.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>7. Managing Agile Projects with JIRA<\/strong><\/h2>\n\n\n\n<p>JIRA\u2019s integration with Agile frameworks makes it essential for modern QA professionals.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Scrum in JIRA<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use <strong>Epics<\/strong> for large features.<\/li>\n\n\n\n<li><strong>Stories<\/strong> represent smaller functionalities.<\/li>\n\n\n\n<li><strong>Sprints<\/strong> are short cycles (usually 2\u20134 weeks).<br>QA testers can log and test stories within each sprint, ensuring consistent feedback.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Kanban in JIRA<\/strong><\/h3>\n\n\n\n<p>Kanban focuses on continuous delivery. QA teams can visualize the flow of work across stages, perfect for ongoing maintenance testing.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Backlog Grooming<\/strong><\/h3>\n\n\n\n<p>QA teams participate in backlog grooming sessions to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Review and prioritize pending test cases<\/li>\n\n\n\n<li>Estimate testing effort<\/li>\n\n\n\n<li>Ensure clear acceptance criteria<\/li>\n<\/ul>\n\n\n\n<p>By learning Agile testing practices in tools like JIRA, students in <strong>Quality assurance software testing courses<\/strong> become industry-ready for Agile or hybrid environments.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>8. Reporting and Analytics<\/strong><\/h2>\n\n\n\n<p>Data-driven insights help improve QA performance. JIRA provides several built-in reports, such as:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Types of JIRA Reports<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Burndown Charts<\/strong>: Show remaining work in a sprint.<\/li>\n\n\n\n<li><strong>Velocity Charts<\/strong>: Display completed tasks per sprint.<\/li>\n\n\n\n<li><strong>Cumulative Flow Diagrams<\/strong>: Visualize bottlenecks.<\/li>\n\n\n\n<li><strong>Bug Trends<\/strong>: Track defect discovery and resolution rates.<\/li>\n<\/ul>\n\n\n\n<p>For <strong>Software testing and quality assurance course<\/strong> learners, these reports demonstrate how to measure progress, identify blockers, and improve sprint velocity.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1024\" height=\"538\" src=\"https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2020\/10\/image-8-1024x538.png\" alt=\"\" class=\"wp-image-31383\" title=\"\" srcset=\"https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2020\/10\/image-8-1024x538.png 1024w, https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2020\/10\/image-8-300x158.png 300w, https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2020\/10\/image-8-768x403.png 768w, https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2020\/10\/image-8.png 1200w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>9. Integrating JIRA with QA and Dev Tools<\/strong><\/h2>\n\n\n\n<p>JIRA integrates seamlessly with several popular tools, making it central to DevOps and QA pipelines.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Common Integrations<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Test Management Tools<\/strong>: Zephyr, Xray, TestRail<\/li>\n\n\n\n<li><strong>Automation Frameworks<\/strong>: Selenium, Cypress, JUnit<\/li>\n\n\n\n<li><strong>CI\/CD Tools<\/strong>: Jenkins, Bamboo, GitHub Actions<\/li>\n\n\n\n<li><strong>Communication Tools<\/strong>: Slack, Microsoft Teams<\/li>\n<\/ul>\n\n\n\n<p>For example, you can link a <strong>Selenium automation test case<\/strong> directly with a JIRA issue, enabling traceability from test script to defect resolution.<br>This practical skill is often included in <strong>Quality assurance software testing courses<\/strong> to help students work in integrated test environments.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>10. Best Practices for Using JIRA in QA<\/strong><\/h2>\n\n\n\n<p>To make the most out of JIRA, QA teams should follow certain best practices:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"> <strong>1. Define Clear Workflows<\/strong><\/h3>\n\n\n\n<p>Map your testing stages accurately from test case creation to closure. Keep statuses simple but meaningful.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"> <strong>2. Use Labels and Filters<\/strong><\/h3>\n\n\n\n<p>Use consistent naming conventions for easier issue tracking (e.g., \u201cRegression,\u201d \u201cSmokeTest\u201d).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>3. Link Related Issues<\/strong><\/h3>\n\n\n\n<p>Connect defects with their corresponding user stories or test cases. This improves traceability and accountability.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>4. Automate Repetitive Tasks<\/strong><\/h3>\n\n\n\n<p>Use <strong>JIRA Automation Rules<\/strong> to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Auto-assign new defects<\/li>\n\n\n\n<li>Change status when pull requests merge<\/li>\n\n\n\n<li>Send email notifications<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>5. Keep Dashboards Updated<\/strong><\/h3>\n\n\n\n<p>Create team dashboards to monitor progress, bug counts, and sprint goals at a glance.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>6. Integrate Test Management Plugins<\/strong><\/h3>\n\n\n\n<p>For complex QA workflows, integrate tools like <strong>Zephyr for JIRA<\/strong> to manage test cases and execution cycles directly within JIRA.<\/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>Even though JIRA is powerful, beginners often face challenges during setup and execution. Let\u2019s address a few:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>1. Complex Configuration<\/strong><\/h3>\n\n\n\n<p>JIRA\u2019s flexibility can be overwhelming.<br><strong>Tip:<\/strong> Start with a pre-built QA template and gradually introduce custom fields.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>2. Poorly Defined Workflows<\/strong><\/h3>\n\n\n\n<p>Overly complex workflows slow down testing.<br> <strong>Tip:<\/strong> Limit statuses to what\u2019s necessary for your QA lifecycle.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>3. Miscommunication Between QA and Dev Teams<\/strong><\/h3>\n\n\n\n<p>Lack of clarity in issue descriptions can lead to delays.<br><strong>Tip:<\/strong> Use clear, detailed bug reports and attach logs or screenshots.<\/p>\n\n\n\n<p>By addressing these challenges early, you\u2019ll improve efficiency and collaboration across teams something every <strong>Software testing and quality assurance course<\/strong> emphasizes in practical sessions.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>12. Real-World Use Case: JIRA in a QA Team<\/strong><\/h2>\n\n\n\n<p>Let\u2019s look at how a QA team in a fintech company uses JIRA:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Requirement Phase:<\/strong>\n<ul class=\"wp-block-list\">\n<li>Product managers log new user stories in JIRA.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Test Case Design:<\/strong>\n<ul class=\"wp-block-list\">\n<li>QA team creates test cases linked to each story.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Execution:<\/strong>\n<ul class=\"wp-block-list\">\n<li>During each sprint, QA executes test cases and logs defects as issues.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Bug Fix &amp; Retest:<\/strong>\n<ul class=\"wp-block-list\">\n<li>Developers resolve issues, QA verifies and closes them.<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Reporting:<\/strong>\n<ul class=\"wp-block-list\">\n<li>Weekly reports summarize open vs. closed defects, sprint velocity, and test coverage.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n<p>This workflow represents what students practice in <strong>Quality assurance software testing courses<\/strong> bridging the gap between classroom learning and industry implementation.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>13. Why QA Professionals Should Learn JIRA<\/strong><\/h2>\n\n\n\n<p>Mastering JIRA isn\u2019t just a technical skill \u2014 it\u2019s a <strong>career accelerator<\/strong>.<br>Employers across industries seek QA professionals who can:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Track and manage test cycles effectively<\/li>\n\n\n\n<li>Communicate clearly using standardized workflows<\/li>\n\n\n\n<li>Integrate JIRA with automation pipelines<\/li>\n<\/ul>\n\n\n\n<p>Whether you\u2019re pursuing a <strong>Software testing and quality assurance course<\/strong> or already in a QA role, adding JIRA expertise to your skill set makes you more valuable and versatile in Agile environments.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>14. Conclusion<\/strong><\/h2>\n\n\n\n<p>JIRA has become the backbone of modern software development and QA processes. From managing test cases and tracking bugs to analyzing reports and integrating with automation tools, it streamlines every aspect of <strong>software testing and quality assurance<\/strong>.<\/p>\n\n\n\n<p>For aspiring QA professionals, enrolling in <strong><a href=\"https:\/\/www.h2kinfosys.com\/courses\/qa-online-training-course-details\/\">Quality assurance software testing courses<\/a><\/strong> that include JIRA training is an excellent way to gain hands-on experience with real-world tools. With structured workflows, customizable dashboards, and deep integration options, JIRA empowers teams to deliver high-quality software faster, smarter, and more efficiently.<\/p>\n\n\n\n<p><strong>Key Takeaway:<\/strong><br>Learning how to use JIRA is more than just mastering a tool; it\u2019s about understanding how modern QA and development teams collaborate. Whether you\u2019re preparing for your first QA role or upgrading your career through a <strong>Software testing and quality assurance course<\/strong>, proficiency in JIRA will make you stand out in today\u2019s Agile-driven industry.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the world of Software testing and quality assurance, efficiency, traceability, and transparency are everything. One tool that stands out as a game-changer in this space is JIRA, a robust project management and bug-tracking solution developed by Atlassian. Whether you\u2019re a QA engineer, project manager, or a student enrolled in Quality assurance software testing courses, [&hellip;]<\/p>\n","protected":false},"author":20,"featured_media":6309,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[],"class_list":["post-6155","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\/6155","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=6155"}],"version-history":[{"count":2,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/6155\/revisions"}],"predecessor-version":[{"id":34301,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/6155\/revisions\/34301"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/media\/6309"}],"wp:attachment":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/media?parent=6155"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/categories?post=6155"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/tags?post=6155"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}