A. What is your idea?
1) Classification
Choose ONE: keep the applicable option and delete the rest.
- Opportunity for improvement
2) Brief description
What happened, what is missing, or what could be better? Focus on the problem or opportunity (not the solution).
Write here:
The amount of information visible in the Dispatch Console is limited by the amount of rows each ticket can have (I think it is 2 or 3 at the moment).
It would be good to have information such as Request /RWT number, Customer number, customer name, Location/Address, Country, Project number visible in the ticket without the need to click on the ticket or hover over it. Most of our Tickets span multiple days, so this would drastically increase the useability of the Dispatch Console for us.
B. Context and scope
1) Who is affected?
Choose ONE or MORE: keep the applicable options and delete the rest.
- Internal users
2) Frequency
Choose ONE: keep the applicable option and delete the rest.
- Daily
C. Value and impact
1) What is the business outcome?
Choose ONE or MORE: keep the applicable options and delete the rest.
- Improves productivity or efficiency
- Reduces cost or manual effort
- Enhances user experience
2) Impact scale
Choose ONE: keep the applicable option and delete the rest.
- 2 — Team / department
3) Workaround
If there is a workaround, describe it briefly. Otherwise write “No workaround”.
Write here:
We are using a self made tool for visual planning as the Dispatch Console does not deliver on what we need
D. Evidence and examples
Attach screenshots, documents, or examples using the buttons below. If helpful, summarize key supporting evidence here.
Write here:
Example of what a Ticket looks like in our tool.
E. Additional details
1) Enter support ticket ID reference (If applicable)
Write here:
…
2) Would you like to participate in validation or early testing?
Answer “Yes/No”.
Write here:
YES