Actions
Task #18743
openTask #18862: Sprint Planning for 06/10/2025 - 17/10/2025
Quotation From RFQ - Ability to Reject an RFQ
Status:
New
Priority:
Normal
Assignee:
-
Start date:
09/17/2025
Due date:
09/17/2025 (about 3 months late)
% Done:
0%
Estimated time:
0:00 h
GitLab ID:
3210
GitLab Milestone:
GitLab Ticket Number:
906
GitLab Time Logged:
0
Lock Timeline Date:
No
gitlab project trace:
Description
A user should have the ability to cancel or reject an RFQ if he does not wish to process.
Acceptance Criteria:¶
-
Cancel/Reject Action
- On the quotation list screen and/or quotation detail screen, users should see an option to Reject RFQ.
- This option should be available only if the quotation is still in the "Requested" state (i.e., before being processed into a quotation).
-
Reason for Rejection
- When the user selects "Reject," a popup or form should appear requiring them to provide a reason for rejection (mandatory field).
- Reasons should be text.
-
Status Update
- Once an RFQ is rejected, its status should update to "Rejected" (or similar label) and be visible in the quotation list.
- The rejection reason should be stored and viewable in the quotation details.
- Once an RFQ is marked as Rejected, it must not be possible to edit or process.
- User should have the option to send Cancellation notifications to the client. This can be optional.
-
Audit/Tracking
- The system should record:
- User who rejected the RFQ
- Date and time of cancellation/rejection
- Reason provided
- The system should record:
-
Permissions
- Only users with appropriate authority should be able to reject an RFQ.
Quotation List Screen:
- Add a Reject button beside "Edit" and "View" actions for RFQs in "Requested" state.
- Clicking it opens a modal to enter a reason and confirm rejection.
Quotation Detail Screen:
- Add a Reject RFQ button next to the current "Update" button.
- Clicking it opens a modal to enter a reason and confirm rejection.
GitLab Sync Log
[]
Actions