Return tracker feedback

Open Beginner friendly
#31 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
html
Domain
design

Research direction

Start with the linked Track My Return — Refund & Return Status prototype and review how return, refund, and amended-return states are represented. Add one example showing a return with an outstanding balance that TP pays off; done means the example is visible and fits the existing state flow.

Written by the indexing model from the issue text.

Description

🖐 awaiting feedback

Your proposed return tracker (Track My Return — Refund & Return Status) looks great. Needless to say, Scott Willoughby and team will be the business POC on all the states for return processing, and whether there is anything else you need to join return states with refund states and amended return states, and whether everything is so linear or there is potential for branching

Can you also add one example of return having balance and TP paying off

Dominant language
HTML
Stars
0
Forks
0
Avg merge
3m
Merged PRs (30d)
11

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from slavingia/prototypes

All issues in slavingia/prototypes

Similar issues

More Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.