/
JIRA Ticket system

JIRA Ticket system

Owned by Ammar Ahmed Butt (Deactivated)
Last updated: Aug 18, 2022
3 min read

Product Team

Issue types

– It can vary from product to product but the basics - will remain the same.

  • Hierarchy level of issue types in Hypr
    -- Each issue type can have its workflow.

  • As soon as a ticket is raised on the “JIRA Service Desk” it gets cloned on “JIRA Software Project” - Fields are shown below.

JIRA Ticket System

Epics

  • High-level Stories.

  • Module Name or Feature Name is given to an Epic. (best practice)

Adding Due dates is mandatory.

Story

Story format (As a <persona>, I want <some goal>, So that <some reason>) - Mandatory Format

Each Story will have following items. (mandatory otherwise Sprint won’t be kicked off.)

Documentation(use cases, UI UX design; it will be 1st approved then kicked off)
A Parent issue (an Epic) attached to it.
Story point estimate
Design attached if Required.
Due Date
Fix Version
Sprint
Labels to identify client (if more than one) + one of these label is mandatory(Product-Development OR Client-Requirement)
Done Criteria/Acceptance Critaria
1 Story Point=1Day=8Hrs – 0.5 SP= 4Hrs – 0.25 SP = 2Hrs
Story Shouldn’t be more than 4 SPs, if more than 4 SPs then it should be divided into two parts.
Each Developer will be assigned Maximum 8 Story Points in a Sprint (if 100% dedicated)

Bugs

Bugs are reported by the QA.

Each bug will have a Parent issue(an Epic) assigned to it. (if they are independent Bugs)
linked with its relevant story/task
If the bug is related to some story, create a subtask under the main ticket, don’t forget to mention all the labels, fix version, due date, Quarter, etc. After adding a subtask(as a bug) comment on the main story, attach the subtask link, and Reopen the ticket.
Due date
Fix Version
Labels (New-issue, Regression-bug, known-issue)
Use Case
Reporoducing steps
Screenshot or Video (using tools http://screencast.com or Free screen recorder for Mac and PC | Loom
PerfectPixel by WellDoneCode use this google extension for comparing websites (testing on layer basis)
Most Reliable App & Cross Browser Testing Platform - (will buy Paid version - tickets will dreactly created from the app.)https://shopdev.atlassian.net/l/c/RX17U2Kx
Application Performance Monitoring & Error Tracking Software (will buy Paid version - Integrated with JIRA.)
Cloud Monitoring as a Service | Datadog

Hotfixes

Urgent issues can be directly deployed to any environment.
Each bug will have a Parent issue(an Epic) assigned to it, linked with its relevant story/task, Due date, Fix Version, Acceptance Criteria are mandatory.

SubTasks

If issues are related to some story, they are supposed to be created as subtasks, under a story. (all fields are supposed to be filled)
Can be created by clicking child issue, Jira doesn’t allow a sprint to be closed in the mentioned case.

Documentation - UI UX Design

All tasks should be tracked on the JIRA board
Design either made on Figma or Adobe Xd should be embedded with the ticket.
https://shopdev.atlassian.net/wiki/spaces/SPM/pages/1713832944https://shopdev.atlassian.net/wiki/spaces/SPM/pages/1713833169
Due dates, Story points are mandatory.
Product Managers will create Wireframes, Use cases, and User flow/journey.
A document for design decision will be created 1st and then further work will be done. https://shopdev.atlassian.net/wiki/spaces/SPM/pages/5070192850

Adding Epic(parent issue) is Mandatory in any case.

 

Related content