Github Task
Overview
This document explains the process of how a task comes to us and what approach do we take towards it.
Task assignment
Task is assigned to us through tickets in Sapphire IMS tool.
How we approach
- After ticket is assigned, we Crate a github task of the corresponding ticket with the steps mentioned below.
- Then, we do analysis of the task and identify impacted files, new components required etc.
- After analysis we provide timelines in the github task.
- We go through all the SDLC steps, have code reviewed and then send the build.
- Once build is gone, we once test in the environment and then close the github task and ticket.
Creating new task in github
- Create github task with Sapphire ticket id.
- Add Ticket description as comment while creating task: Ticket Description:
- Add the following comments:
Planning Timeline
Planned Start Date | Planned End Date | Planned Effort hrs | Actual Start Date | Actual End Date | Actual Effort hrs | Comments |
---|
Development Timeline
Planned Start Date | Planned End Date | Planned Effort hrs | Actual Start Date | Actual End Date | Actual Effort hrs | Comments |
---|
Unit Testing Timeline
Planned Start Date | Planned End Date | Planned Effort hrs | Actual Start Date | Actual End Date | Actual Effort hrs | Comments |
---|
Review Timeline
Planned Start Date | Planned End Date | Planned Effort hrs | Actual Start Date | Actual End Date | Actual Effort hrs | Comments |
---|
Documentation Timeline
Planned Start Date | Planned End Date | Planned Effort hrs | Actual Start Date | Actual End Date | Actual Effort hrs | Comments |
---|
Review
Review Comments | Changes Completed |
---|
Impact Analysis Comments
Unit Tests
Sr Num | Test Case | Expected Result | Actual Result | Test Case Status |
---|
Build Status
Testing | Production |
---|
Commit Links
Code | Unit Testing Proofs |
---|
Version | Date | Developed By | Information Classification | Reviewed By | Approved By |
---|---|---|---|---|---|
1.0 | 11-08-2020 | Gunjan | INTERNAL | Prasan | Prasan |