Enatega Customer Application: Cancelled Orders Display history Issue
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- mobile-dev
Research direction
Start by reproducing the cancellation flow in the Enatega Customer Application and trace how Order History separates Current Orders from past statuses. Done means cancelled orders appear in Past Orders with a Cancelled status and the relevant order details, without appearing in Current, Completed, or Delivered sections.
Written by the indexing model from the issue text.
Description
Describe the bug
When an order is cancelled, it is still displayed under the "Current Orders" section. Instead, the cancelled order should be moved to the "Past Orders" section with the status marked as "Cancelled" for better organization and clarity.
To Reproduce
Steps to reproduce the behavior:
Go to 'Enatega Customer Application'
Click on 'Restaurants' and select any food add to cart.
Place an order.
See error Cancel that order now go to profile menu button and select Order History under Current heading there is the history of In progress, Delivered orders but not the orders that has been cancelled by the customer in any case.
Expected behavior
They should display all relevant details such as: Order ID, Restaurant name, Items in the order, Reason for cancellation (if provided),
Date and time of cancellation.
These orders should not appear under the "Completed" or "Delivered" sections but should remain listed for tracking purposes.
Screenshots
Image
Image
Smartphone (please complete the following information):
Device: [e.g. Infinix Hot 50]
OS: [e.g. Android]
Browser [e.g.Application]
Version [e.g. 14]
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from raymondjames090/food-ordering-system-java-eclipse
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
All issues in raymondjames090/food-ordering-system-java-eclipse
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100