When a request clearly explains the problem, who it affects, and the business, it becomes much easier to evaluate and prioritize. A well-written request also reduces the back-and-forth. If the team has to ask follow-up questions to understand what you mean or why it matters, this will stall the process.
below is an example of what to include:
Description — Summary describing the current gap or limitation. what's missing that should exist?
Use Case — Describe the real-world scenario where this can be used in your workflow and be beneficial for your process.
Problem to be Solved — What specifically needs to change and why its necessary? You can suggest a solution and show examples.Please also add screenshot showing where you would like the new feature in the OMS.