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

44 (5 Closed, 39 open or in progress)

Proposed sprint start

Fri 23-Oct-2026 (first full working week starts Mon 26-Oct)

Last synced with Jira

09-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)

Change

Tickets

What was done on this page

Removed from fix version 2.4 (Jira total went from 50 to 44)

STOP-144 (locked-door cases), 165 (mobile number checkbox), 171 (village as default address), 243 (ABHA face authentication), 408 (auto-populate mobile number), 581 (Type of House options), 583 (cooking fuel options)

Moved to the "Removed from 2.4" table. Please confirm which release they moved to.

Added to fix version 2.4

STOP-628 – TB Screening Form takes excessively long to load (Highest, Analysis, Ashutosh)

Added to section I and to the allocation. Needs triage; size unknown.

Status changed

STOP-351 (search bars) is now Closed

Moved to the Closed table.

Assignee changed in Jira

STOP-603, 604, 620 (TPT) now with Ashutosh; STOP-606 (Dashboard) now with Rupesh

See the team input below for the proposed owners.

Team input applied to the proposal

Release 2.4 priorities

Priority focus for this release, in order:

  1. TPT module improvements – STOP-603, 604, 620

  2. Contact Tracing module improvements – STOP-602, 618, 619 (plus the related Confirmed TB follow-up change STOP-600)

  3. Inventory module – additional fields – STOP-623

  4. Wrong-password attempts counter on login – STOP-599

  5. Dashboard change – STOP-606

  6. Everything else – registration and location capture, referrals and counselling, ABHA/ABDM, bug fixes, sync, platform tasks (sections F to J 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

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

STOP-603

TPT follow-up: remove "Adherence to Medicines", rename ADR to "Side effects"

Highest

Todo/Open

Ashutosh

Chetan (Backend), Vanitha (API support)

Deepshika

Build together with 600 and 604. Old records must still display.

STOP-604

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.

STOP-620

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

STOP-618

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?

STOP-602

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.

STOP-619

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?

STOP-600

Confirmed TB follow-up: rename title, remove "Adherence to Medicines", ADR to "Side Effects"

Medium

Todo/Open

Rupesh

Ashutosh (Mobile), Vishwa (API)

Deepshika

Related change 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

STOP-623

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

STOP-599

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

STOP-606

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

STOP-509

Populate village master with PIN codes

Medium

Ready for Development

Puneet Sharma

Vishwa (API/data)

Deepshika

Blocks STOP-412. Start first. Data/backend work, so moved from Puneet (mobile) to Vishwa. Villages without a PIN code must be listed to Product.

STOP-412

Pincode and Residential Area captured once per village (supersedes GPS approach STOP-308)

Highest

Todo/Open

Sehjot

Rohit (Mobile), Sehjot (API)

Deepshika

Depends on 509. STOP-404 depends on this. Work is mostly app-side, so mobile leads.

STOP-404

Auto-select "Elderly" (60+) and "Urban Slum" in Key Population / Risk Factors

Medium

In Development

Deepak

Deepak (Mobile)

Brijesh

No change. Urban Slum rule needs Residential Area from 412. Confirm villages are not mixed slum / non-slum.

STOP-414

Location capture changes (Digipin only, progress bar, edit location)

High

In Development

Puneet Sharma

Puneet (Mobile), Sehjot (API)

Brijesh

No change on the mobile side; stays with Puneet.

STOP-164

Anthropometry screen changes

High

Todo/Open

Agraj Parashar

Ankit (Mobile), Sneha (UI)

Brijesh

Group with 433 (Examine button behaviour).

STOP-433

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.

STOP-557

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

STOP-576

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.

STOP-528

Beneficiary not moving to Liquid Culture referral card

High

Todo/Open

Ankit

Ankit (Mobile)

Brijesh

No change.

STOP-506

Add "Clinical Assessment and Diagnosis" referral queue

Medium

Todo/Open

Deepak

Deepak (Mobile)

Brijesh

No change.

STOP-504

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.

STOP-552

TrueNat: close test order when test not conducted

Low

Pending QA

Brijesh

Dev complete

Brijesh

STOP-553

TrueNat: auto-close open orders at EoD

Low

Pending QA

Brijesh

Dev complete

Brijesh

H. ABHA / ABDM

Ticket

Summary

Jira priority

Jira status

Current Jira assignee

Proposed dev owner(s)

QA

Notes / dependencies

STOP-136

ABDM M2 Phase 1 – General OPD flow

Highest

In Development

Rohit

Rohit (Mobile), Vanitha (API)

Deepshika

Largest item in the release. Vanitha added for the API side. Rohit to confirm how much is already done.

STOP-386

Unable to create ABHA on Play Store build

High

Analysis

Deepshika (QA)

Vanitha (API), Rohit (Mobile)

Deepshika

Needs developer investigation; currently sitting with QA.

STOP-182

"Yes" button not clickable for ABHA card download

High

In QA

Deepshika

Dev complete

Deepshika

STOP-524

ABHA screen UI breaks on tablet; consent text layout

Medium

Todo/Open

Rupesh

Sneha (UI)

Brijesh

I. Bugs, stability and sync

Ticket

Summary

Jira priority

Jira status

Current Jira assignee

Proposed dev owner(s)

QA

Notes / dependencies

STOP-628

NEW – TB Screening form takes excessively long to load and stays in a loading state

Highest

Analysis

Ashutosh

Ashutosh (Mobile), Sehjot (API, performance support)

Deepshika

Added to 2.4 since the last sync. Needs triage; check whether related to 502 (card counts) and 252 (performance testing). Size unknown.

STOP-502

Card counts (All HH / All Beneficiary / Non-Household) fluctuating

Highest

Analysis

Ashutosh

Ashutosh (Mobile)

Deepshika

No change.

STOP-449

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.

STOP-523

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.

STOP-556

Wrong toast count for registered family members; inconsistent purple colour

High

Todo/Open

Agraj Parashar

Ankit (Mobile), Sneha (UI)

Brijesh

Count logic to Ankit, colour to Sneha.

STOP-607

OK / Cancel buttons overlap in Chief Complaint popup

Low

Todo/Open

Ankit

Sneha (UI)

Brijesh

Layout-only fix, moved to Sneha.

STOP-163

"Add HoF member" alert; HoF icon on card

High

Pending QA

Rohit

Dev complete

Brijesh

STOP-593

Default UAT URL for Connect Camp Hub in UAT build

Medium

Pending QA

Brijesh

Dev complete

Brijesh

J. Platform, DevOps and performance

Ticket

Summary

Jira priority

Jira status

Current Jira assignee

Proposed dev owner(s)

QA

Notes / dependencies

STOP-252

Performance testing of STOP_TB (reopened)

High

Reopened

Sehjot

Sehjot (API)

Deepshika

No change.

STOP-580

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.

STOP-491

Soft launch ID generator on 2 camp laptops

Low

Todo/Open

Syed

Chetan, Syed to coordinate

Brijesh

STOP-564

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.

K. Closed in 2.4

Ticket

Summary

Last Jira assignee

Note

STOP-308

PIN code and address via GPS

Agraj Parashar

Closed; superseded by STOP-412 (GPS unworkable offline).

STOP-351

Search bars in ADR (treatment follow-up, TPT follow-up) and Key population / risk factors

Shivani

Newly Closed since last sync.

STOP-397

Duplicate work orders / duplicate names on TrueNat

Sehjot

Closed

STOP-460

Optimise beneficiary photo size to prevent sync failures

Rohit

Closed

STOP-582

House ownership radio button (Rented / Owned)

Ashutosh

Closed

L. Removed from 2.4 since last sync

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

STOP-144

Handling locked-door cases in HH enumeration

Puneet Sharma

STOP-165

Mobile number checkbox in HH registration

Ashutosh

STOP-171

Village name as default address

Ankit

STOP-243

Create ABHA using Face authentication

Rohit

STOP-408

Auto population of mobile number from HH registration

Rohit

STOP-581

Update "Type of House" options

Rupesh

STOP-583

Update "Primary source of fuel used for cooking" options

Rupesh

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 38 unique open tickets being allocated). The five Closed tickets and the removed tickets are excluded. "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

Rohit

Mobile

4

STOP-136, 412, 523, 386

Two large, high-risk items (ABDM OPD flow, incremental sync), one medium (village-level capture), one investigation

Full (~95–105%)

Ashutosh

Mobile

6

STOP-602, 618, 619, 600, 628, 502

Contact Tracing (one medium-large, rest small to medium), plus two Highest-priority bugs under analysis (form load time, card counts)

Full (~100–110%); may rise if the two bugs are deep

Deepak

Mobile

4

STOP-404, 449, 506, 623

Auto-select rules, a device-level bug, referral queue, Inventory (scope unknown)

Medium (~65–75%); may rise if Inventory is large

Puneet

Mobile

3

STOP-414, 599, 606

Location capture (large, in development), login change (small), dashboard (needs clarifications)

Medium (~70–80%)

Ankit

Mobile

5

STOP-576, 528, 164, 433, 556

Referral and screening bug fixes, anthropometry and Examine button, toast count

Medium (~60–70%); has headroom

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 (~75–85%)

Vanitha

API

6

STOP-136, 599, 386, 603, 604, 620

ABDM APIs (large), login attempt count, ABHA investigation, API support on TPT

Medium-high (~70–80%)

Vishwa

Backend

6

STOP-509, 557, 606, 602, 618, 600

Village master data, data fix, dashboard queries, contact-tracing API changes

Medium (~50%); headroom for overflow

Sehjot

Backend

5

STOP-412, 623, 252, 414, 628

Village-level fields, inventory API, performance work, location API, form-load investigation support

Medium (~45–50%)

Sneha

UI

5

STOP-524, 504, 607, 164, 556

Small layout, copy and colour changes

Low (~25–30%); can also support screen designs for TPT and Contact Tracing

Deepshika

QA

16

STOP-136, 182, 252, 386, 412, 502, 509, 523, 557, 599, 600, 603, 604, 606, 620, 628

Fewer but heavier tickets: ABDM, sync, village-level capture, TPT forms, performance

Over-allocated (~170–190%) with regression

Brijesh

QA

22

STOP-163, 164, 404, 414, 433, 449, 491, 504, 506, 524, 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 (~140–160%) with regression

Rupesh

Delivery Manager

1

STOP-564

Non-dev environment setup

Not a delivery load

Key observation: with Puneet in the mobile team and TPT with a backend developer, developer load is now balanced, and Ankit, Deepak and Puneet have some headroom. QA remains well above what two people can test in the same period and is still the bottleneck, so spare mobile capacity is best used for developer self-testing and for QA hand-over preparation.

Tickets moving away from their current Jira assignee

Current Jira assignee

Open tickets held today

Moving to

Rupesh (Delivery Manager)

7

6 move to developers (STOP-524 to Sneha; 600, 602, 618 to Ashutosh; 606 to Puneet; 623 to Deepak); STOP-564 stays

Puneet Sharma (Mobile)

3

STOP-414 and 599 stay with him; STOP-509 moves to Vishwa (data work)

Agraj Parashar

3

STOP-164 and 556 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

7

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)

Approximate sprint duration (TBD – not confirmed)

Item

Approximate (TBD)

Basis

Sprint start

Fri 23-Oct-2026

Proposed

Development phase

~4–5 weeks, i.e. to roughly late November

Seven tickets left the release, five mobile developers, TPT with a Backend developer; festival days around Diwali (~8-Nov)

Priority items (TPT, Contact Tracing, Inventory, Login, Dashboard) dev complete

~3–4 weeks, i.e. mid to late 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–3 weeks after code freeze

QA load is still above capacity in the same window

Complete 2.4 build after QA

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, 628, 449, 557 plus the 509 and 412 pair. Roughly 3–4 weeks of development (to about late November) and 1 week of QA, with the remaining tickets moved to a follow-up sprint.

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

Village master PIN code data source; list of villages with no PIN

Product / Data team

STOP-509, STOP-412

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, 556, 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 7 removed tickets (144, 165, 171, 243, 408, 581, 583) move to, and is STOP-628 confirmed as in scope for 2.4?

Shivani / Rupesh

Scope and allocation

17

TPT is proposed to Chetan (lowest backend load) with Vanitha supporting. Confirm Chetan, or choose Sehjot / Vishwa, and confirm whether any app-side screen change in TPT needs a mobile developer to pair.

Mithun / Rupesh

STOP-603, 604, 620

Risks

Review and sign-off

Name

Role

Sign-off

Rupesh

Delivery Manager

Shivani

Product Manager

Madhava

BSA

Vanshika

BSA

Mithun

Engineering

Syed

Senior Manager