Skip to main content

Include manual change reasons in reporting data

  • June 25, 2026
  • 0 replies
  • 1 view

tomgreenwood
Superhero (Employee)
Forum|alt.badge.img+24

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 PSO Reporting data tables don’t include the reason or reason value on Activity Status updates, if this was included then reports could be produced on users who have made manual changes such as fixing an activity to a resource or updating the status of an activity.

B. Context and scope

1) Who is affected?
Choose ONE or MORE: keep the applicable options and delete the rest.

  • Internal users
  • Customers
  • Partners

2) Frequency
Choose ONE: keep the applicable option and delete the rest.

  • Frequently

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
  • Enables new capability

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:
reports can be created on scheduling data but this is not recommended by product development

D. Evidence and examples

Attach screenshots, documents, or examples using the buttons below. If helpful, summarize key supporting evidence here.

Write here:

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