Missing Record of Previous Orders in Enatega Multivendor Rider App.

Open

#1,792 opened on Jul 14, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 48/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Quiet
Tech stack: javascript, react-native
Domain: frontend, mobile

Research direction

Start by locating the rider app's order and navigation screens, then trace how current and completed orders are loaded. Review existing order-list patterns before deciding where the history section belongs. Done means riders can open a section showing their previous orders and relevant past-delivery details.

Written by the indexing model from the issue text.

Description

Issue: Missing Record of Previous Orders in Rider App
Description:
In rider app, there is currently no record of previous orders displayed. It is crucial to have a section that shows the rider's history of previous orders for reference and record-keeping.

Impact:
Order Tracking: The absence of a record of previous orders can make it difficult for riders to track their history and details of past deliveries.

Accountability: Previous order records are essential for accountability and resolving any issues related to past orders.

Steps to Reproduce:
Access the rider app.
Navigate through the app to find a section that displays the rider's history of previous orders.
Observe that there is no record of previous orders available.
Expected Resolution:
You need to implement a section in the rider app that shows a rider's history of previous orders. This will enable riders to track their deliveries and provide an essential reference point for resolving any past order-related issues.

Dominant language: JavaScript
Stars: 0
Forks: 0
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing 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.