Jira requirements and stories
Source: Jira export, October 25, 2026. This is a read-only snapshot, not a live status check. The workbook says the stories are first-pass and may change. The FRD is the requirements reference. Jira's rule IDs differ from the FRD's IDs. [Start here, rows 2–14.]
Learners' proposed catalog tasks are described in detail. The export also records unresolved choices that could change what a learner sees or can do. A written story shows intended behavior, not observed use or a working feature.
What is in the workbook
All six sheets and every populated cell were read, including inline replies inside acceptance criteria and questions. There are 79 RFP requirement rows, 43 Catalog stories, 37 extracted question rows and 14 build-task rows. The question sheet is a selected list: many more questions remain inside the stories. All sheets, rows and columns are visible. There are no comments, merged cells, charts or images; four drawing XML parts are empty. Formula text and cached totals were checked against the source rows. No workbook was changed.
| Module and epic | Pod | RFP requirements | Stories in this export |
|---|---|---|---|
| Profile, SUNY-84 | 4 | 4 | 0 |
| Catalog, SUNY-85 | 1 | 13 | 43 |
| Enrollment, SUNY-86 | 4 | 11 | 0 |
| Finance, SUNY-87 | 6 | 10 | 0 |
| Learner Center, SUNY-88 | 5 | 5 | 0 |
| Credentials, SUNY-89 | 5 | 5 | 0 |
| Communication, SUNY-90 | 3 | 7 | 0 |
| Feedback, SUNY-91 | 2 | 3 | 0 |
| Support, SUNY-92 | 3 | 4 | 0 |
| Reporting, SUNY-93 | 2 | 17 | 0 |
Source: Modules, rows 2–12. Zero stories here does not establish that no requirements work exists elsewhere.
Of the 43 stories, 33 are Ready for Sprint and 10 In Development. Eighteen have SUNY Sprint 1 assigned: 17 staff stories and SUNY-174, the Commerce search analysis. None is marked complete. The workbook defines Ready for Sprint as not started. Role counts are 14 Public, 6 Learner, 13 Campus Personnel, 4 NCSIM Admin, 3 Instructor and 3 Employer. These are story counts, not audience size or priority. [User stories, rows 2–44; Start here, row 13.]
The RFP responses preserve the earlier proposal
The RFP sheet puts the original requirement beside PruTech's response and a Jira status. Some requirement text ends mid-sentence in the actual cells, for example 2.2, 2.3, 2.12, 4.3 and 6.2. Use the full RFP for complete wording. Salesforce capability and benefit claims below are vendor proposals, not independently checked platform facts or measured outcomes.
| Sheet rows; requirement IDs | What the response proposes |
|---|---|
| 2–5; 1.1–1.4 | Self-service profile and history; validation, approvals and audit; downloadable/shareable certificates and badges; Global ID and campus synchronization; employer accounts, single/bulk enrollment, sponsorship payments and participation reports. Only 1.1 is In Development; other RFP rows are Ready for Sprint. |
| 6–18; 2.1–2.13 | Statewide catalog in Education Cloud/Experience Cloud, campus synchronization or direct maintenance, course/program detail, search by category/date/instructor/location/delivery, transfer information, saved searches and alerts, printable PDF, maps/radius/directions, funding filters, waitlist position and timed offers, fees/discounts/deadlines, credential preparation and testing conditions. These broad promises need comparison with later rules. |
| 19–29; 3.1–3.11 | Individual and guest registration; capacity and timestamp-based waitlists; employer CSV/manual bulk enrollment and group payment; staff quick registration with permitted overrides; accountless registration for selected activity types; withdrawal/refund requests; employer learner replacement preserving payment; channel preferences and notifications; Global ID matching to prevent duplicates. |
| 30–39; 4.1–4.10 | Campus gateway routing, receipts returned to the learner record, aid disbursement and direct NYS integration, funding applications and tracking, financial reporting, retained campus finance systems, post-payment confirmation, individual/bulk refunds under campus rules, gateway-specific payment choices. Row 30 says home/associated campus for routing, while row 16 says the course's campus. This needs clarification for cross-campus learners. |
| 40–44; 5.1–5.5 | Orientation released at relevant milestones; learning-system schedules/assignments/progress; dashboard alerts, job/salary information and skill mapping; AI recommendations; achievement badges. Claims that these motivate learners are not research results. |
| 45–49; 6.1–6.5 | Progress, deadlines and completion history; Salesforce ID linked to Global ID, with name/SSN offered as an identity lookup example; prior credential migration or synchronization; verification queues, audit and a proposed SUNY Verified label. This does not establish a universal SSN requirement. |
| 50–56; 7.1–7.7 | Staff messages without coding, templates, targeting, scheduling and view tracking; preferences with essential messages retained; external-system and mixed-system communications; support appointments; email/SMS/in-app delivery; responsive and accessible interfaces. The assertion that the platform provides compliance is not a test result. |
| 57–59; 8.1–8.3 | Course/instructor feedback, configured surveys and reviews, structured ratings and free text, routing and reporting under privacy rules. These describe planned collection, not supplied learner research. |
| 60–63; 9.1–9.4 | Existing helpdesk/chat/knowledge integrations, conversational bot and human transfer, guided support, feedback capture and ticket status. The response cites WCAG 2.1 here. |
| 64–80; 10.1–10.17 | Warehouse synchronization and role-based reporting; skills/jobs; evaluations and progress; attendance/discussion/assignment engagement; voluntarily supplied demographics; completion and program comparison; compliance and survey reports; unduplicated headcount; activity categories; credit participation/transitions; completion and employment/wage outcomes; campus financial/partner reports; learner grades. Row 78 distinguishes recorded completion from self-reported job/salary surveys. Correlation is described, not established causation. Row 74 proposes AI queries and trend detection, not an available analysis. |
Several responses differ from the October architecture direction: guest enrollment, learning-system/helpdesk/state-aid connections, live labor-market data and the scope of AI. The newer export date does not make the older proposal responses current decisions.
Every Catalog story
The row is the exact source locator. Story IDs are US-CAT followed by the number below. Read the story's rules and questions together: several appear more settled in the acceptance criteria than in the questions beside them.
| Row; story; Jira key | Intended experience and remaining conditions |
|---|---|
| 2; 001; SUNY-122 | Search published title, description, keywords and campus without an account. Instructor is excluded from keyword search; dates belong in filters/sort. Keep query/filter context and result/page counts. Exclude private/draft items. Multiword matching, partial words, page size and failure states remain open. |
| 3; 002; SUNY-123 | Browse statewide without choosing a campus. Show parent/child relationships, Coming Soon and eligible waitlists. Hide draft/internal/archived/employer-only content. Mixed child states and empty parents remain open. |
| 4; 003; SUNY-124 | Combine campus, location, category, modality, cost and funding filters; keep selections on zero results. In-person/online/hybrid are named. Multiple-selection logic, date/price boundaries, missing values and funding vocabulary need agreement. |
| 5; 004; SUNY-125 | Map/radius search asks permission before device location and supports manual entry if denied. A reply ranks chosen campus, entered address, then consented device location. Teaching address versus campus, radius units, virtual/multiple locations and unavailable coordinates remain unresolved. Randomization/upcoming offering is only a suggested fallback. |
| 6; 005; SUNY-126 | Preferred campus influences ranking without removing other campuses. Explicit campus filter overrides it. Profile address then consented device location are fallbacks. Per-search controls, multiple affiliations and neutral fallback need definition. |
| 7; 006; SUNY-127 | Discover documented credit-evaluation relationships, source and target campuses, and last-verified dates. Do not promise credit. Source authority, freshness, expiry and unavailable feeds remain open. |
| 8; 007; SUNY-128 | Show objectives, prerequisites, funding, schedule, format and the owning campus's brand/contact inside shared navigation. Preferred campus does not change the owner. Coming Soon applies without registerable children. Required fields, shared-campus credit and mixed states remain open. |
| 9; 008; SUNY-129 | Show the correct section fee, discount conditions and deadline before enrollment. Catalog does not collect payment. Total mandatory costs, unknown versus free, price ranges, time zone and price protection remain open. |
| 10; 009; SUNY-130 | Show only documented credit-evaluation destinations and verification dates. Authority, stale/conflicting information, conditions and target-specific wording remain open. |
| 11; 010; SUNY-131 | Show credential purpose, criteria and recorded awarding authority. No unsupported award promise; viewing does not issue a credential. |
| 12; 011; SUNY-132 | Separate discoverability from registration readiness. Show Coming Soon, Open, Full/Waitlist, Closed or Cancelled as appropriate. Enrollment owns readiness. Waitlist wording, mixed sections, cutoffs and stale seats remain open. |
| 13; 012; SUNY-133 | Funding information and external application links only; NCSIM does not process applications. SUNY supplies final wording. Older questions still refer to funding-intent capture and screening, so the row contains wording that needs reconciliation. |
| 14; 013; SUNY-134 | Check age from profile DOB, show other prerequisites for self-assessment, and show an unable-to-verify message when DOB is absent. Catalog's ineligible label does not block viewing or starting registration. Age reference date, bounds, guardian rules and final verification owner remain open. |
| 15; 014; SUNY-135 | Documented pathways count completed required activities only, not enrollment or unrelated completions. No credit guarantee. R1 treats pathways as programs; microcredential-specific work is deferred to R2 pending SUNY leadership. Substitutions, repeat completions and weighting remain questions. |
| 16; 015; SUNY-136 | Campus staff create own-campus records with title, description and modality. Registerable sessions need valid dates; fee-based offerings need price. Source is stamped. Permissions, draft versus publication requirements and shared ownership questions have inline deferrals; an “even split” reply does not resolve the single-owner rule. |
| 17; 016; SUNY-137 | Staff edit Salesforce-owned fields, retain change history and trigger a communication event for schedule changes. SIS-owned fields stay read-only. Replies accept date validation, schedule event and audit, but defer permissions. Approval, affected audiences, concurrent changes and learner choices remain open. |
| 18; 017; SUNY-138 | Maintain sections, independent dates, instructors and capacity; prevent negative capacity and invalid dates. No ready section means Coming Soon. One instructor is a temporary assumption. Zero capacity, recurrence, asynchronous sessions, clashes and cancellation effects remain deferred. |
| 19; 018; SUNY-139 | Archive own-campus records, remove from active discovery and keep history. Respect SIS archive updates. Archive versus unpublish/cancel/delete, active commitments, restoration and historic links remain open. |
| 20; 019; SUNY-140 | Maintain fees, discounts and deadlines with audit and source protection. Free versus missing, fee types, existing registrants' price protection and notices need decisions. |
| 21; 020; SUNY-141 | Maintain age bounds and narrative prerequisites, reject minimum above maximum. Only age is automatically evaluated here. Requirements versus recommendations, section overrides, exceptions and change notices need definition. |
| 22; 021; SUNY-142 | Maintain documented, active cross-campus recognition and verification dates. Same-campus relationship is not a cross-campus transfer. Approval, evidence, expiry and changed relationships are explicitly deferred in the replies. |
| 23; 022; SUNY-143 | Describe credential designation, criteria and awarding body without issuing credentials. Evidence fields and approval need remain unsettled. |
| 24; 023; SUNY-144 | Validate before publishing to the intended audience; authorized publishing has no separate approval workflow in the rule. SIS owns its publication state. Coming Soon conflicts with a cited FRD Published/Open rule. Replies defer the detailed transition and permission questions. |
| 25; 024; SUNY-145 | Central staff inspect statewide records, owner, source and status, with separate edit/override/delete permissions. Cross-campus nonpublic access is controlled. Issue routing, duplicate rules and exception ownership remain open. |
| 26; 025; SUNY-146 | Use common recognition labels, source/target campuses and verification dates while campuses own content. Governance, versioning and effect on existing records remain unresolved. |
| 27; 026; SUNY-147 | Instructors see active assignments. Ended/unassigned work is not current. Story notes no corresponding Catalog high-level requirement. Inline replies question restricted visibility but do not supply a clear approved alternative. |
| 28; 027; SUNY-148 | Instructors read assigned objectives, prerequisites, schedules, locations and materials without editing source fields. Ownership, unpublished/historic/cancelled access and material release rules are deferred. |
| 29; 028; SUNY-149 | Show assigned instructors registration, available-seat and waitlist counts separately. Counts do not change seats. Holds, unpaid/withdrawn records, refresh and whether identities are exposed need clarification. |
| 30; 029; SUNY-150 | Signed-in favorites are private, deduplicated and separate from registration. Explicit FRD-only scope candidate. Saved inaccessible/archived items and ordering remain open; no guest favorites. |
| 31; 030; SUNY-151 | Employer checks positive whole-number cohort size against seats, with shortfall shown and no reservation. Allocation sources, split sections, holds and replacement periods remain open. |
| 32; 031; SUNY-152 | Employer worksite guides location ranking; explicit location wins. No invented location or other organization's private listings. Affiliation, multiple worksites and missing-location behavior need agreement. |
| 33; 032; SUNY-153 | Employer-only offerings stay private until authorized manual public release under the agreement. No automatic date release and no independent seat changes by Catalog. A reply favors the top of the waitlist for released seats; partial release, approvals and notices remain deferred. |
| 34; 033; SUNY-154 | Staff inspect synchronized source data; sections link to existing parents; malformed updates do not overwrite valid fields. Show Coming Soon before sections arrive. Cadence, field ownership, failed/stale updates and correction responsibility remain open. |
| 35; 034; SUNY-155 | Sort by start date, alphabet, modality or price while retaining filters. Acceptance criteria keep campus/proximity groups ahead of chosen sort. Questions explicitly challenge that precedence. Tie-breaking, missing values and course-level date/price are unresolved. |
| 36; 035; SUNY-156 | Stable shareable detail URLs obey current permissions every time. A Share button, preserved section/search context and unavailable-page treatment remain undecided. |
| 37; 036; SUNY-157 | Signed-in interest in Coming Soon can lead to an availability alert, separate from favorites or a reserved seat. Marked possible FRD gap/release dependency. Consent, withdrawal, duplicates, triggers and delivery owner remain open. |
| 38; 037; SUNY-158 | Guest asks about an offering without an account; selected course/section passes into the inquiry. Acceptance criteria require first/last name and email, with inquiry text described. Exact fields, consent, routing, acknowledgement, response time and changed visibility remain questions. No enrollment or hold. |
| 39; 038; SUNY-159 | Authorized employer sees public plus its organization's private/hybrid offerings; direct links also enforce access. Affiliation/license, multiple organizations, expiry and public release remain open. |
| 40; 039; SUNY-160 | Provisional central-admin ownership correction with one owner, updated branding and audit. FRD versus October rules conflict; effect on SIS authority, registrations, billing and agreements is deferred. |
| 41; 040; SUNY-161 | Exceptional permanent deletion needs separate authority, approval, stakeholder communication and retained audit. Normal retirement is archive. Retention, existing commitments and dependent records remain unresolved. This story is not in Sprint 1. |
| 42; 041; SUNY-172 | SIS publish/unpublish/archive changes update the correct Education Cloud record; failures are logged and duplicates prevented. Data Cloud receives a later asynchronous copy, which is not the original update. |
| 43; 042; SUNY-173 | Only approved NCSIM-owned changes may go back for campus retrieval. Protect SIS fields, campus access and feedback loops. Retrieval does not prove the campus applied the change. Outbound use case remains conditional on SUNY approval. |
| 44; 043; SUNY-174 | Commerce search analysis repeats story 001's search content. Its Sprint 1 assignment does not establish that public search is implemented or that Commerce is the approved choice. |
Stories 001–040 were created October 14; 041–042 October 20; 043 October 21. Inline replies have no speaker or reply date in this export. “Does not need to be answered now” is a recorded deferral, not an answer and not a rule for our review.
Open questions sheet
All rows 2–38 were read. They repeat selected questions from the story sheet: pagination and taxonomy (2–3, 5–7, 37–38); status/hierarchy (4, 10, 13–14, 17, 22–23, 26); campus preference (8); recognition authority (9, 12, 24, 28); ownership and permissions (11, 16, 18–20, 25, 27, 36); section changes (21); pathway counting (15); employer allocation/access (29–31, 34–35); synchronization (32); sorting (33). The 37 rows are not 37 independently resolved decisions or a complete backlog of uncertainty.
What staff-facing work had started
Screens in build, rows 2–15, records tasks rather than screen captures or verified implementation:
- SUNY-168–170: custom fields/objects, including employer-course links and error logs. Assigned to Vishnu Vijay Zanwar, Chirag Singh and Sakshi Bhuyar; In Development.
- SUNY-176–183: program/course/learning pages, edit buttons, status paths, offering schedules, equivalency, prerequisites, employer-course links and employer/campus account pages. Some are In Development; edit, offering and equivalency pages are in Dev Peer Review. Several specify the Academic Operations app and System Admin profile. This does not prove the final role permissions are ready.
- SUNY-184: instructor assigned-offering list, Sai Sudeshna Belluri, Ready for Sprint.
- SUNY-196–197: date and capacity validation, in Dev Peer Review. These tasks say end date cannot be less than start date. Stories 015/017 reject equal dates too. Same-day offerings could be affected; compare the FRD and intended date/time rules before judging the implementation.
Tasks were created October 19, 22 and 23. The snapshot provides no test results or completed end-to-end learner flow.
Evidence and questions to carry forward
E-014, detailed stories do not settle every learner-facing rule. Stories 008, 011, 012, 034 and 037 record cost, availability, funding, sorting and inquiry decisions alongside open questions. Confidence is strong about the source content; current agreement and implementation are unknown. These points should guide the FRD comparison and later journey choice.
E-015, the export preserves different stages of scope. RFP responses promise funding applications, guest registration and learning-system integration, while later stories and architecture narrow these. Confidence is strong that the supplied records differ. This does not establish an unauthorized scope change: approval records may exist elsewhere. The current draft FRD and decision owners must settle the affected boundaries.
E-016, visible development status is mostly staff Catalog work. Eighteen stories are assigned to Sprint 1, including the Commerce analysis; the 14 build tasks are staff/data work. Confidence is strong for the October 25 snapshot, not live delivery status. This supports finding a useful public journey contribution without claiming the team has implemented nothing for learners.
Reading coverage: Start here rows 1–14, Modules rows 1–12, RFP requirements rows 1–80, User stories rows 1–44, Open questions rows 1–38, Screens in build rows 1–15. All columns, formula/cached totals, visibility and auxiliary-content checks covered. Workbook layout contains no merged cells or visual diagrams that change reading order. Source link checked locally.
Related topics: cross-source findings.