cagov/ui-claim-tracker issues and pull requests

#50 - Setup accessibility scanning on Staging

Issue - State: closed - Opened by lomky over 3 years ago
Labels: Engineering, Size: S

#49 - Setup linting

Issue - State: closed - Opened by lomky over 3 years ago - 3 comments
Labels: Engineering, Size: M

#49 - Setup linting

Issue - State: closed - Opened by lomky over 3 years ago - 3 comments
Labels: Engineering, Size: M

#48 - Integrate automated browser tests

Issue - State: open - Opened by lomky over 3 years ago - 1 comment
Labels: Engineering, Size: L, Type: Developer Experience

#48 - Integrate automated browser tests

Issue - State: open - Opened by lomky over 3 years ago - 1 comment
Labels: Engineering, Size: L, Type: Developer Experience

#47 - Integrate Azure application monitoring and set up alerts

Issue - State: closed - Opened by lomky over 3 years ago
Labels: Engineering, Size: S

#47 - Integrate Azure application monitoring and set up alerts

Issue - State: closed - Opened by lomky over 3 years ago
Labels: Engineering, Size: S

#46 - Add Storybook framework

Issue - State: closed - Opened by lomky over 3 years ago
Labels: Engineering, Size: M

#46 - Add Storybook framework

Issue - State: closed - Opened by lomky over 3 years ago
Labels: Engineering, Size: M

#45 - Add the Bootstrap design system

Issue - State: closed - Opened by lomky over 3 years ago
Labels: Engineering, Size: M

#45 - Add the Bootstrap design system

Issue - State: closed - Opened by lomky over 3 years ago
Labels: Engineering, Size: M

#44 - Choose and integrate an internationalization library

Issue - State: closed - Opened by lomky over 3 years ago - 2 comments
Labels: Engineering, Size: M

#44 - Choose and integrate an internationalization library

Issue - State: closed - Opened by lomky over 3 years ago - 2 comments
Labels: Engineering, Size: M

#43 - Choose and integrate an accessibility scanner for development

Issue - State: closed - Opened by lomky over 3 years ago - 1 comment
Labels: Engineering, Size: S

#43 - Choose and integrate an accessibility scanner for development

Issue - State: closed - Opened by lomky over 3 years ago - 1 comment
Labels: Engineering, Size: S

#42 - Choose and integrate a test framework

Issue - State: closed - Opened by lomky over 3 years ago - 4 comments
Labels: Engineering, Size: L

#42 - Choose and integrate a test framework

Issue - State: closed - Opened by lomky over 3 years ago - 4 comments
Labels: Engineering, Size: L

#41 - Update task.md

Pull Request - State: closed - Opened by kalvinwang over 3 years ago - 1 comment

#41 - Update task.md

Pull Request - State: closed - Opened by kalvinwang over 3 years ago - 1 comment

#40 - Add CODEOWNERS, PR template

Pull Request - State: closed - Opened by kalvinwang over 3 years ago

#40 - Add CODEOWNERS, PR template

Pull Request - State: closed - Opened by kalvinwang over 3 years ago

#39 - Initial Typescript nextJS app

Pull Request - State: closed - Opened by lomky over 3 years ago
Labels: Engineering

#39 - Initial Typescript nextJS app

Pull Request - State: closed - Opened by lomky over 3 years ago
Labels: Engineering

#38 - Summarize accessibility requirements from WCUG

Issue - State: closed - Opened by nicoleslaw over 3 years ago - 1 comment
Labels: Design

#38 - Summarize accessibility requirements from WCUG

Issue - State: closed - Opened by nicoleslaw over 3 years ago - 1 comment
Labels: Design

#37 - What database should we use?

Issue - State: closed - Opened by kalvinwang over 3 years ago - 2 comments
Labels: Engineering

#37 - What database should we use?

Issue - State: closed - Opened by kalvinwang over 3 years ago - 2 comments
Labels: Engineering

#36 - Work with CDT to set up our initial infrastructure in Azure

Issue - State: closed - Opened by kalvinwang over 3 years ago - 1 comment
Labels: Engineering, Size: L

#36 - Work with CDT to set up our initial infrastructure in Azure

Issue - State: closed - Opened by kalvinwang over 3 years ago - 1 comment
Labels: Engineering, Size: L

#35 - Decide and document approach to using UIMOD as source of truth

Issue - State: closed - Opened by kalvinwang over 3 years ago - 2 comments
Labels: Engineering, Size: L

#35 - Decide and document approach to using UIMOD as source of truth

Issue - State: closed - Opened by kalvinwang over 3 years ago - 2 comments
Labels: Engineering, Size: L

#34 - Write initial tech spec for BPO integration

Issue - State: closed - Opened by kalvinwang over 3 years ago - 1 comment
Labels: Engineering

#34 - Write initial tech spec for BPO integration

Issue - State: closed - Opened by kalvinwang over 3 years ago - 1 comment
Labels: Engineering

#33 - Write discovery sprint brief

Issue - State: closed - Opened by AngelQuicksey over 3 years ago
Labels: Design

#33 - Write discovery sprint brief

Issue - State: closed - Opened by AngelQuicksey over 3 years ago
Labels: Design

#32 - Document screen reader basics and share with team

Issue - State: closed - Opened by nicoleslaw over 3 years ago - 2 comments
Labels: Design, Size: M

#32 - Document screen reader basics and share with team

Issue - State: closed - Opened by nicoleslaw over 3 years ago - 2 comments
Labels: Design, Size: M

#31 - Should we use Typescript instead of Javascript (ES6)?

Issue - State: closed - Opened by kalvinwang over 3 years ago - 1 comment
Labels: Engineering

#31 - Should we use Typescript instead of Javascript (ES6)?

Issue - State: closed - Opened by kalvinwang over 3 years ago - 1 comment
Labels: Engineering

#30 - Coordinate with EDD to understand required pre-launch testing/review processes

Issue - State: closed - Opened by dianagriffin-zz over 3 years ago - 2 comments
Labels: Product, Size: M

#30 - Coordinate with EDD to understand required pre-launch testing/review processes

Issue - State: closed - Opened by dianagriffin-zz over 3 years ago - 2 comments
Labels: Product, Size: M

#29 - Coordinate planning and implementation of linking between Claim Tracker and UIO

Issue - State: closed - Opened by dianagriffin-zz over 3 years ago - 2 comments
Labels: Product, Size: L

#29 - Coordinate planning and implementation of linking between Claim Tracker and UIO

Issue - State: closed - Opened by dianagriffin-zz over 3 years ago - 2 comments
Labels: Product, Size: L

#28 - Gather requirements based on UIMOD data fields and handling

Issue - State: closed - Opened by dianagriffin-zz over 3 years ago - 3 comments
Labels: Product

#28 - Gather requirements based on UIMOD data fields and handling

Issue - State: closed - Opened by dianagriffin-zz over 3 years ago - 3 comments
Labels: Product

#27 - Update Claim Tracker product brief

Issue - State: closed - Opened by dianagriffin-zz over 3 years ago - 1 comment
Labels: Product

#27 - Update Claim Tracker product brief

Issue - State: closed - Opened by dianagriffin-zz over 3 years ago - 1 comment
Labels: Product

#26 - Draft a product vision statement

Issue - State: closed - Opened by dianagriffin-zz over 3 years ago
Labels: Product

#26 - Draft a product vision statement

Issue - State: closed - Opened by dianagriffin-zz over 3 years ago
Labels: Product

#25 - Should we use Next.js instead of our previous Node/Express/Webpack setup?

Issue - State: closed - Opened by lomky over 3 years ago - 2 comments
Labels: Engineering

#25 - Should we use Next.js instead of our previous Node/Express/Webpack setup?

Issue - State: closed - Opened by lomky over 3 years ago - 2 comments
Labels: Engineering

#24 - Adds issues templates

Pull Request - State: closed - Opened by lomky over 3 years ago

#24 - Adds issues templates

Pull Request - State: closed - Opened by lomky over 3 years ago

#23 - Create usability testing interview guide and note-taking documents

Issue - State: closed - Opened by AngelQuicksey over 3 years ago - 5 comments
Labels: Design, Size: M

#23 - Create usability testing interview guide and note-taking documents

Issue - State: closed - Opened by AngelQuicksey over 3 years ago - 5 comments
Labels: Design, Size: M

#22 - Create and execute S4 recruitment plan

Issue - State: closed - Opened by AngelQuicksey over 3 years ago - 2 comments
Labels: Design, Size: M

#22 - Create and execute S4 recruitment plan

Issue - State: closed - Opened by AngelQuicksey over 3 years ago - 2 comments
Labels: Design, Size: M

#21 - Create claimant research plan for one status

Issue - State: closed - Opened by AngelQuicksey over 3 years ago
Labels: Design, Size: M

#21 - Create claimant research plan for one status

Issue - State: closed - Opened by AngelQuicksey over 3 years ago
Labels: Design, Size: M

#20 - Refine claim status documentation

Issue - State: closed - Opened by AngelQuicksey over 3 years ago
Labels: Design

#20 - Refine claim status documentation

Issue - State: closed - Opened by AngelQuicksey over 3 years ago
Labels: Design

#19 - Obtain documentation of claim statuses in UIO

Issue - State: closed - Opened by AngelQuicksey over 3 years ago
Labels: Design, Design Ops

#19 - Obtain documentation of claim statuses in UIO

Issue - State: closed - Opened by AngelQuicksey over 3 years ago
Labels: Design, Design Ops

#18 - Review Nava's status content with stakeholders

Issue - State: closed - Opened by AngelQuicksey over 3 years ago
Labels: Design

#18 - Review Nava's status content with stakeholders

Issue - State: closed - Opened by AngelQuicksey over 3 years ago
Labels: Design

#17 - Accessibility checkin

Issue - State: closed - Opened by AngelQuicksey over 3 years ago
Labels: Design

#17 - Accessibility checkin

Issue - State: closed - Opened by AngelQuicksey over 3 years ago
Labels: Design

#16 - Document accessibility check-in criteria

Issue - State: closed - Opened by AngelQuicksey over 3 years ago

#16 - Document accessibility check-in criteria

Issue - State: closed - Opened by AngelQuicksey over 3 years ago

#15 - Validate service blueprint with client

Issue - State: closed - Opened by AngelQuicksey over 3 years ago
Labels: Design

#15 - Validate service blueprint with client

Issue - State: closed - Opened by AngelQuicksey over 3 years ago
Labels: Design

#14 - Set up content stakeholder meeting

Issue - State: closed - Opened by AngelQuicksey over 3 years ago
Labels: Design

#14 - Set up content stakeholder meeting

Issue - State: closed - Opened by AngelQuicksey over 3 years ago
Labels: Design

#13 - Identify high level questions for web content and policy stakeholders

Issue - State: closed - Opened by AngelQuicksey over 3 years ago - 2 comments
Labels: Design

#13 - Identify high level questions for web content and policy stakeholders

Issue - State: closed - Opened by AngelQuicksey over 3 years ago - 2 comments
Labels: Design

#12 - Draft claim status content for usability testing

Issue - State: closed - Opened by AngelQuicksey over 3 years ago - 1 comment
Labels: Design, Size: L

#12 - Draft claim status content for usability testing

Issue - State: closed - Opened by AngelQuicksey over 3 years ago - 1 comment
Labels: Design, Size: L

#11 - Identify the content, policy, and legal points of contact for content review

Issue - State: closed - Opened by AngelQuicksey over 3 years ago
Labels: Design, Design Ops

#11 - Identify the content, policy, and legal points of contact for content review

Issue - State: closed - Opened by AngelQuicksey over 3 years ago
Labels: Design, Design Ops

#10 - Document accessibility requirements

Issue - State: closed - Opened by AngelQuicksey over 3 years ago - 1 comment
Labels: Design, Size: S

#10 - Document accessibility requirements

Issue - State: closed - Opened by AngelQuicksey over 3 years ago - 1 comment
Labels: Design, Size: S

#9 - Draft logic model for claim tracker impact

Issue - State: closed - Opened by AngelQuicksey over 3 years ago
Labels: Design

#9 - Draft logic model for claim tracker impact

Issue - State: closed - Opened by AngelQuicksey over 3 years ago
Labels: Design

#8 - Gather claim status query data (call centers)

Issue - State: closed - Opened by AngelQuicksey over 3 years ago - 2 comments
Labels: Product

#8 - Gather claim status query data (call centers)

Issue - State: closed - Opened by AngelQuicksey over 3 years ago - 2 comments
Labels: Product

#7 - Gather claim status system data

Issue - State: closed - Opened by AngelQuicksey over 3 years ago - 1 comment
Labels: Product

#7 - Gather claim status system data

Issue - State: closed - Opened by AngelQuicksey over 3 years ago - 1 comment
Labels: Product

#6 - Define desirable claim tracker metrics

Issue - State: closed - Opened by AngelQuicksey over 3 years ago - 1 comment
Labels: Product

#5 - Draft archetypes + moments that matter

Issue - State: closed - Opened by AngelQuicksey over 3 years ago - 1 comment
Labels: Design, Size: S

#4 - Identify and review existing status content / identify gaps

Issue - State: closed - Opened by AngelQuicksey over 3 years ago - 1 comment
Labels: Design

#3 - Review existing blueprints of user journey

Issue - State: closed - Opened by AngelQuicksey over 3 years ago
Labels: Design

#2 - Task [template]

Issue - State: closed - Opened by AngelQuicksey over 3 years ago

#1 - User Story [Template]

Issue - State: closed - Opened by AngelQuicksey over 3 years ago

GitHub / cagov/ui-claim-tracker issues and pull requests