Overview
Module | STOP TB Mobile App (TBMJA) |
Release / Version | 2.4 – Jira fix version 2.4 |
Purpose | Define and lock the scope of features/modules/fixes going into v2.4 so BSAs, Delivery Manager, Product and Engineering have one place to review owners, bandwidth and timeline before the sprint begins. |
Total Jira tickets | 39 (7 Closed, 32 open or in progress) |
Proposed sprint start | Fri 23-Oct-2026 (first full working week starts Mon 26-Oct) |
Last synced with Jira | 12-Oct-2026 (see "Changes since last sync" below) |
Page status | DRAFT for review – proposed owners, allocation and duration are not confirmed |
PRD reference | TBMJA PRD (v186) |
Changes since last sync (Jira fix version 2.4)
Jira total went from 44 to 39 tickets.
Change | Tickets | What was done on this page |
|---|---|---|
Removed from fix version 2.4 | STOP-136 (ABDM M2 OPD flow), 182 (ABHA card download button), 386 (ABHA creation on Play Store build), 524 (ABHA screen on tablet), 509 (village master PIN codes) | Moved to the "Removed from 2.4" table. All ABHA/ABDM work has now left the release, so that section is gone. Please confirm where they moved (open question 16). |
Newly Closed | STOP-506 (referral queue, closed under Shivani), STOP-628 (TB Screening form load time) | Moved to the Closed table. |
Status changed | STOP-404 (auto-select Elderly / Urban Slum): In Development to Pending QA. STOP-603 (TPT follow-up): Todo to In Development (Ashutosh) | Updated in the ticket tables. Note on 603 below. |
Assignee changed in Jira | STOP-600 (Rupesh to Ashutosh), STOP-556 (Agraj to Ashutosh) | Both match this proposal; STOP-556 is now proposed to Ashutosh with Sneha on colour. |
Earlier changes (previous sync): 7 tickets (STOP-144, 165, 171, 243, 408, 581, 583) left the release; STOP-628 was added; STOP-351 was closed.
Team input applied to the proposal
Puneet Sharma is a mobile developer and is part of the delivery team. He keeps STOP-414 and STOP-599 and picks up STOP-606.
The TPT module goes to a Backend developer. STOP-603, 604 and 620 are proposed to Chetan (with Vanitha supporting on APIs). Note: STOP-603 is already In Development under Ashutosh in Jira, so the hand-over needs to be confirmed (open question 17).
Ashutosh owns Contact Tracing: STOP-602, 618, 619 and 600, plus STOP-502 (card counts) and STOP-556 (toast count). Ankit keeps the referral and anthropometry items.
Release 2.4 priorities
Priority focus for this release, in order:
TPT module improvements – STOP-603, 604, 620
Contact Tracing module improvements – STOP-602, 618, 619 (plus the related Confirmed TB follow-up change STOP-600)
Inventory module – additional fields – STOP-623
Wrong-password attempts counter on login – STOP-599
Dashboard change – STOP-606
Everything else – registration and location capture, referrals and counselling, bug fixes, sync, platform tasks (sections F to I below)
Team and roles
Role | People |
|---|---|
Mobile developers | Rohit, Deepak, Ankit, Ashutosh, Puneet |
Backend developers | Sehjot, Vishwa, Chetan |
API developer | Vanitha |
UI developer | Sneha |
QA | Deepshika, Brijesh |
Delivery Manager | Rupesh |
Product Manager | Shivani |
Engineering | Mithun |
BSA | Madhava, Vanshika |
Senior Manager | Syed |
How to read the ticket tables
Current Jira assignee shows who the ticket is assigned to in Jira today. Proposed dev owner(s) shows who should own it based on the roles above and the kind of work (mobile app logic, API/backend, UI/layout/copy, DevOps, data). Jira has not been changed by this page.
Tickets currently held by Rupesh or Syed (not delivery developers), by Agraj Parashar (not in the delivery team list), or by nobody have been re-proposed to the right developer.
No effort estimates are included because the team has not estimated individual tickets yet. The allocation and duration below are based on ticket counts and kind of work and are deliberately approximate.
Sneha is assumed to own pure UI/layout/copy changes; mobile developers own app logic.
Public holidays and planned leave are not yet deducted. Diwali falls around 8-Nov-2026 and the festival period will reduce availability in late October and November (to be confirmed against the company holiday calendar).
Scope by theme
A. P0 – TPT module (Backend developer owned)
Ticket | Summary | Jira priority | Jira status | Current Jira assignee | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|---|
TPT follow-up: remove "Adherence to Medicines", rename ADR to "Side effects" | Highest | In Development | Ashutosh | Chetan (Backend), Vanitha (API support) | Deepshika | Already in development under Ashutosh. Confirm hand-over to Chetan or let Ashutosh finish 603. Build together with 600 and 604. Old records must still display. | |
TPT follow-up: replace outcome status options; "Other" becomes optional Remarks | Highest | Todo/Open | Ashutosh | Chetan (Backend), Vanitha (API support) | Deepshika | 5 open clarifications (outcome mapping, date rules, removed "Developed active TB" redirect, Remarks limit, migration of old values). Blocks start. | |
TPT: "Start TPT" and "TPT Follow Up" buttons, 6 regimens, first-visit details in follow-up | Highest | Todo/Open | Ashutosh | Chetan (Backend), Vanitha (API support) | Deepshika | 4 open questions (regimen month mapping, 250–500 words rule, default instruction text, follow-up gating). |
B. P0 – Contact Tracing module (Ashutosh owned)
Ticket | Summary | Jira priority | Jira status | Current Jira assignee | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|---|
Add "Household" option, view/edit/update after submit, "Any other Significant Information" (500 words) | Highest | Todo/Open | Rupesh | Ashutosh (Mobile), Vishwa (API) | Brijesh | Open question: should Household reuse the existing Members screen? | |
HHC tracing follow-up: Referred to = PHI / TB Camp, Remarks, auto Date, "Recommend for ATT Treatment" | Medium | Todo/Open | Rupesh | Ashutosh (Mobile), Vishwa (API) | Brijesh | Test both Counsellor and Surveillance Officer roles. Old referral values (TU/DH/CHC/PHC, DOTS) must still display. | |
Enable household-member "follow-up" button for Surveillance Officer role | Highest | Todo/Open | Unassigned | Ashutosh (Mobile) | Brijesh | Blocker question: "Surveillance Officer" is not in PRD roles. Does the role exist in the app or must it be created? | |
Confirmed TB follow-up: rename title, remove "Adherence to Medicines", ADR to "Side Effects" | Medium | Todo/Open | Ashutosh | Ashutosh (Mobile), Vishwa (API) | Deepshika | Jira assignee now matches the proposal. Related to TPT; keep labels consistent with 603 (Chetan). |
C. P0 – Inventory module
Ticket | Summary | Jira priority | Jira status | Current Jira assignee | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|---|
Additional Improvements in Inventory Modules (additional fields) | Highest | Todo/Open | Rupesh | Deepak (Mobile), Sehjot (API) | Brijesh | Ticket has no description or field list. Scope and size unknown until Product (Shivani) provides the field specification. |
D. P0 – Login: wrong-password attempts
Ticket | Summary | Jira priority | Jira status | Current Jira assignee | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|---|
Wrong-password error should show remaining attempts (max 5) | High | Todo/Open | Puneet Sharma | Puneet (Mobile), Vanitha (API) | Deepshika | No change on the mobile side. Lockout message after attempt 5 is still TBD. Decide whether to show attempts for a non-existent username (security). Backend must expose remaining count. |
E. P0 – Dashboard
Ticket | Summary | Jira priority | Jira status | Current Jira assignee | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|---|
Screening Coverage Summary: "Total Eligible Population for TB Screening" with demographic breakdown | Low | Todo/Open | Rupesh | Puneet (Mobile), Vishwa (API) | Deepshika | 3 open clarifications (definition of eligible population, filter rule, replace or sit alongside STOP-500 breakdown). Depends on STOP-500 (2.3, in QA). Jira priority is Low but the release priority list places it in P0. |
F. Registration and location capture
Ticket | Summary | Jira priority | Jira status | Current Jira assignee | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|---|
Pincode and Residential Area captured once per village (supersedes GPS approach STOP-308) | Highest | Todo/Open | Sehjot | Rohit (Mobile), Sehjot (API) | Deepshika | Depended on STOP-509 (village master PIN codes), which has been removed from 2.4. Confirm the data source or release for 509 (open question 9). Work is mostly app-side, so mobile leads. | |
Auto-select "Elderly" (60+) and "Urban Slum" in Key Population / Risk Factors | Medium | Pending QA | Deepak | Dev complete (Deepak) | Brijesh | Development done. Urban Slum rule needs Residential Area from 412, so full verification may wait for 412. | |
Location capture changes (Digipin only, progress bar, edit location) | High | In Development | Puneet Sharma | Puneet (Mobile), Sehjot (API) | Brijesh | No change; stays with Puneet. | |
Anthropometry screen changes | High | Todo/Open | Agraj Parashar | Ankit (Mobile), Sneha (UI) | Brijesh | Group with 433 (Examine button behaviour). | |
Examine button state reflects complete form submission | Low | Todo/Open | Ashutosh | Ankit (Mobile) | Brijesh | Moved to Ankit so 164 and 433 (same Examine screens) sit with one developer, and to free Ashutosh for Contact Tracing. | |
District, Block and Village names blank for 222 records | Highest | Todo/Open | Vishwa | Vishwa (API/data) | Deepshika | No change. Data fix plus root-cause check so it does not recur. |
G. Referrals, counselling and TrueNat
Ticket | Summary | Jira priority | Jira status | Current Jira assignee | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|---|
New TB Screening questions: Abnormal functionality not showing in 2.3.25 | Highest | Todo/Open | Ankit | Ankit (Mobile) | Brijesh | No change. Regression from 2.3.25; fix early. | |
Beneficiary not moving to Liquid Culture referral card | High | Todo/Open | Ankit | Ankit (Mobile) | Brijesh | No change. | |
NPY and DOTS helper text in Counselling Section C | Medium | Analysis | Sehjot | Sneha (UI) | Brijesh | Copy/helper text is a UI task, not backend. Hindi translation must be provided by Product before release. | |
TrueNat: close test order when test not conducted | Low | Pending QA | Brijesh | Dev complete | Brijesh | ||
TrueNat: auto-close open orders at EoD | Low | Pending QA | Brijesh | Dev complete | Brijesh |
H. Bugs, stability and sync
Ticket | Summary | Jira priority | Jira status | Current Jira assignee | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|---|
Card counts (All HH / All Beneficiary / Non-Household) fluctuating | Highest | Analysis | Ashutosh | Ashutosh (Mobile) | Deepshika | No change. | |
Android Wi-Fi captive-portal check disconnects on networks without internet validation | Highest | Todo/Open | Syed | Deepak (Mobile) | Brijesh | Android-level bug, so a mobile developer. Needs device/network setup for testing. | |
Incremental beneficiary sync for large datasets | High | Todo/Open | Rohit | Rohit (Mobile), Chetan (API) | Deepshika | Chetan added for the backend side. High regression risk; test with more than 500 beneficiaries. | |
Wrong toast count for registered family members; inconsistent purple colour | High | Todo/Open | Ashutosh | Ashutosh (Mobile), Sneha (UI) | Brijesh | Jira assignee now matches the proposal. Count logic to Ashutosh, colour to Sneha. | |
OK / Cancel buttons overlap in Chief Complaint popup | Low | Todo/Open | Ankit | Sneha (UI) | Brijesh | Layout-only fix, moved to Sneha. | |
"Add HoF member" alert; HoF icon on card | High | Pending QA | Rohit | Dev complete | Brijesh | ||
Default UAT URL for Connect Camp Hub in UAT build | Medium | Pending QA | Brijesh | Dev complete | Brijesh |
I. Platform, DevOps and performance
Ticket | Summary | Jira priority | Jira status | Current Jira assignee | Proposed dev owner(s) | QA | Notes / dependencies |
|---|---|---|---|---|---|---|---|
Performance testing of STOP_TB (reopened) | High | Reopened | Sehjot | Sehjot (API) | Deepshika | No change. | |
Push production builds via MDM (Intune); sunset Play Store releases | High | Todo/Open | Agraj Parashar | Chetan (DevOps) | Brijesh | Pipeline work, so a backend/DevOps developer. Needs the production device group (Krishna) and 4–5 test devices. | |
Soft launch ID generator on 2 camp laptops | Low | Todo/Open | Syed | Chetan, Syed to coordinate | Brijesh | ||
Local environment setup on Deepsikha's and Pratiksha's laptops | Highest | Todo/Open | Rupesh | Rupesh to arrange (non-dev) | – | Stays with Rupesh. Prerequisite for QA handover. |
J. Closed in 2.4
Ticket | Summary | Last Jira assignee | Note |
|---|---|---|---|
PIN code and address via GPS | Agraj Parashar | Closed; superseded by STOP-412 (GPS unworkable offline). | |
Search bars in ADR (treatment follow-up, TPT follow-up) and Key population / risk factors | Shivani | Closed | |
Duplicate work orders / duplicate names on TrueNat | Sehjot | Closed | |
Optimise beneficiary photo size to prevent sync failures | Rohit | Closed | |
Add "Clinical Assessment and Diagnosis" referral queue | Shivani | Newly Closed since last sync. | |
House ownership radio button (Rented / Owned) | Ashutosh | Closed | |
TB Screening form takes excessively long to load | Ashutosh | Newly Closed since last sync. |
K. Removed from 2.4
These tickets are no longer in the Jira fix version 2.4. Please confirm the release they moved to.
Ticket | Summary | Last known Jira assignee | Removed in |
|---|---|---|---|
ABDM M2 Phase 1 – General OPD flow | Rohit | Latest sync | |
"Yes" button not clickable for ABHA card download | Deepshika | Latest sync | |
Unable to create ABHA on Play Store build | Deepshika | Latest sync | |
Populate village master with PIN codes | Puneet Sharma | Latest sync | |
ABHA screen UI breaks on tablet; consent text layout | Rupesh | Latest sync | |
Handling locked-door cases in HH enumeration | Puneet Sharma | Earlier sync | |
Mobile number checkbox in HH registration | Ashutosh | Earlier sync | |
Village name as default address | Ankit | Earlier sync | |
Create ABHA using Face authentication | Rohit | Earlier sync | |
Auto population of mobile number from HH registration | Rohit | Earlier sync | |
Update "Type of House" options | Rupesh | Earlier sync | |
Update "Primary source of fuel used for cooking" options | Rupesh | Earlier sync |
Proposed allocation and load summary (approximate, TBD)
One view of the complete allocation for a sprint starting 23-Oct-2026. "Tickets" counts every open ticket a person is involved in (where two people share a ticket, it counts for both, so the column adds up to more than the 31 unique open tickets being allocated). Closed and removed tickets are excluded; STOP-404 is included as it is still with the developer's name and in QA. "Load" is relative to what one person can reasonably deliver in a roughly 6-week sprint after allowing for festival days and normal overheads (meetings, reviews, bug-fixing, support). It is not based on ticket-level estimates.
Person | Role | No. of tickets | Tickets | Kind of work | Approx. load |
|---|---|---|---|---|---|
Ashutosh | Mobile | 6 | STOP-602, 618, 619, 600, 502, 556 | Contact Tracing (one medium-large, rest small to medium), a Highest-priority bug under analysis (card counts), toast count fix | Full (~85–95%); may rise if STOP-502 is deep |
Puneet | Mobile | 3 | STOP-414, 599, 606 | Location capture (large, in development), login change (small), dashboard (needs clarifications) | Medium (~65–75%) |
Rohit | Mobile | 2 | STOP-412, 523 | Incremental sync (large, high-risk), village-level capture (medium) | Low-medium (~45–55%); has headroom |
Ankit | Mobile | 4 | STOP-576, 528, 164, 433 | Screening and referral bug fixes, anthropometry and Examine button | Low-medium (~45–55%); has headroom |
Deepak | Mobile | 3 | STOP-404 (Pending QA), 449, 623 | Device-level bug, Inventory (scope unknown); 404 already dev complete | Low (~35–45%); may rise if Inventory is large |
Chetan | Backend (TPT owner) / DevOps | 6 | STOP-603, 604, 620, 523, 580, 491 | TPT module (medium to large, blocked by open questions), incremental sync API, MDM pipeline, ID generator rollout | Medium-high (~70–80%) |
Vishwa | Backend | 5 | STOP-557, 606, 602, 618, 600 | Data fix, dashboard queries, contact-tracing API changes | Medium (~40–45%) |
Sehjot | Backend | 4 | STOP-412, 623, 252, 414 | Village-level fields, inventory API, performance work, location API | Low-medium (~35–40%) |
Vanitha | API | 4 | STOP-599, 603, 604, 620 | Login attempt count, API support on TPT | Low-medium (~35–40%); ABDM work has left the release |
Sneha | UI | 4 | STOP-504, 607, 164, 556 | Small layout, copy and colour changes | Low (~20%); can also support screen designs for TPT and Contact Tracing |
Deepshika | QA | 11 | STOP-252, 412, 502, 523, 557, 599, 600, 603, 604, 606, 620 | Sync, village-level capture, TPT forms, Contact Tracing follow-up, performance | Over-allocated (~120–135%) with regression |
Brijesh | QA | 20 | STOP-163, 164, 404, 414, 433, 449, 491, 504, 528, 552, 553, 556, 576, 580, 593, 602, 607, 618, 619, 623 | Many small form, UI and bug verifications plus Contact Tracing and Inventory | Over-allocated (~130–150%) with regression |
Rupesh | Delivery Manager | 1 | STOP-564 | Non-dev environment setup | Not a delivery load |
Key observation: with the ABHA/ABDM work out of the release, most developers now have headroom, especially Rohit, Ankit, Deepak, Vanitha, Sehjot and Sneha. QA is still above capacity and remains the bottleneck, though less than before. Spare developer capacity is best used for self-testing and for QA hand-over preparation, or to pull some of the removed tickets back in if Product wants that.
Tickets moving away from their current Jira assignee
Current Jira assignee | Open tickets held today | Moving to |
|---|---|---|
Rupesh (Delivery Manager) | 5 | 4 move to developers (STOP-602 and 618 to Ashutosh; 606 to Puneet; 623 to Deepak); STOP-564 stays |
Puneet Sharma (Mobile) | 2 | STOP-414 and 599 stay with him |
Agraj Parashar | 2 | STOP-164 to Ankit (with Sneha), STOP-580 to Chetan |
Syed (Senior Manager) | 2 | STOP-449 to Deepak, STOP-491 to Chetan |
Unassigned | 1 | STOP-619 to Ashutosh |
Developers, moved on team input or to match the kind of work | 5 | STOP-603, 604, 620 (Ashutosh to Chetan, TPT to a Backend developer); STOP-433 (Ashutosh to Ankit); STOP-504 (Sehjot to Sneha); STOP-607 (Ankit to Sneha); STOP-412 (Sehjot to Rohit for the app side, Sehjot keeps API) |
STOP-600 and STOP-556 are now assigned to Ashutosh in Jira and match this proposal.
Approximate sprint duration (TBD – not confirmed)
Item | Approximate (TBD) | Basis |
|---|---|---|
Sprint start | Fri 23-Oct-2026 | Proposed |
Development phase | ~3–4 weeks, i.e. to roughly mid to late November | 12 tickets have left the release and 3 more are closed or in QA; five mobile developers with TPT on a Backend developer; festival days around Diwali (~8-Nov) |
Priority items (TPT, Contact Tracing, Inventory, Login, Dashboard) dev complete | ~3 weeks, i.e. mid November | TPT is blocked by open clarifications; Contact Tracing with Ashutosh is the longest mobile path; Inventory depends on a missing spec |
QA, regression and UAT | Runs alongside development, with a tail of ~2 weeks after code freeze | QA is still above capacity in the same window |
Complete 2.4 build after QA | Early to mid December 2026 (TBD) | QA-bound; assumes open questions are closed in the first week |
These are rough ranges to be replaced once each developer provides ticket estimates and the holiday calendar is confirmed.
Open questions and blockers
# | Item | Needed from | Affects |
|---|---|---|---|
1 | Can we run a short hotfix sprint first, covering only the major requirements, and take the rest in a later sprint? With Diwali and other festivals falling in late October and November, a smaller first sprint may be more realistic. Candidate scope: TPT (603, 604, 620), Contact Tracing (602, 618, 619, 600), Inventory (623, once specified), Login attempts (599), Dashboard (606), and the critical bugs 576, 502, 449, 557 plus 412. Roughly 3 weeks of development (to about mid November) and 1 week of QA, with the remaining tickets moved to a follow-up sprint. Since the release is now smaller, a single sprint may also be workable. | Rupesh / Shivani / Mithun / Syed | Entire release plan |
2 | Inventory "additional fields" – no description or field list in the ticket | Shivani / Madhava | STOP-623 |
3 | TPT outcome clarifications (5 questions) | Shivani / Vanshika | STOP-604 |
4 | TPT regimen mapping, "250–500 words" rule, default instruction text, Follow-up gating (4 questions) | Shivani | STOP-620 |
5 | Does the "Surveillance Officer" role exist in the app? What else can it access? | Shivani / Madhava | STOP-619 |
6 | Household option: same Members screen or new form? | Shivani | STOP-618 |
7 | Eligible population definition, filter rule and relation to STOP-500 breakdown | Shivani / Vanshika | STOP-606 |
8 | Lockout message after the 5th wrong attempt; show attempts for unknown usernames? | Shivani / Engineering | STOP-599 |
9 | STOP-509 (village master PIN codes) has left 2.4, but STOP-412 depends on it. Which release does 509 go to, and is 412 still deliverable in 2.4? | Product / Data team / Rupesh | STOP-412, 404 |
10 | Hindi translation of NPY / DOTS helper text | Product | STOP-504 |
11 | Confirm hand-over of work from Agraj Parashar (assigned in Jira but not in the delivery team list) | Rupesh / Mithun | 164, 580 |
12 | Update Jira assignees to match this page once the proposal is agreed (TPT currently with Ashutosh in Jira) | Rupesh | All |
13 | Ticket-level estimates from each developer and QA | Each team member | Allocation and duration |
14 | Leave and public-holiday calendar for 23-Oct to end of December | Rupesh | All dates |
15 | Can QA capacity be increased (extra tester, BSA-led UAT, developers self-testing small UI tickets)? | Rupesh / Mithun | QA timeline |
16 | Which release did the 12 removed tickets move to? In particular, is the whole ABHA/ABDM block (136, 182, 386, 524, 243) intentionally deferred? With developer headroom, does Product want any of them pulled back into 2.4? | Shivani / Rupesh | Scope and allocation |
17 | TPT is proposed to Chetan (Backend) with Vanitha supporting. STOP-603 is already In Development under Ashutosh: confirm hand-over to Chetan or let Ashutosh finish it. Also confirm Chetan or choose Sehjot / Vishwa, and whether any app-side TPT screen change needs a mobile developer to pair. | Mithun / Rupesh | STOP-603, 604, 620 |
Risks
QA capacity is still above what two testers can cover in the sprint window. Mitigations are in open question 15.
TPT and Contact Tracing are blocked by unresolved PRD questions. Highest-priority tickets (604, 619, 620) still have open clarifications.
TPT owned by a Backend developer: if the TPT changes include screen or form changes in the app, they may need mobile support (open question 17). STOP-603 is already in development with Ashutosh, so there is a risk of duplicate or lost work during hand-over.
STOP-412 depends on STOP-509, which has left 2.4. Without the village PIN code data, 412 cannot be completed (open question 9).
Sequencing dependencies: 603 + 604 + 600 to be built together (Chetan and Ashutosh must align on wording).
STOP-623 has no requirement, so its size and Deepak's load are unknown.
Scope is still moving (12 tickets removed and 3 closed over the last two syncs), so allocation and dates may change again.
Festival period in late October and November will reduce availability across the team.
Review and sign-off
Name | Role | Sign-off |
|---|---|---|
Rupesh | Delivery Manager | |
Shivani | Product Manager | |
Madhava | BSA | |
Vanshika | BSA | |
Mithun | Engineering | |
Syed | Senior Manager |