ucdavis / ucdavis/Purchasing

Work in progress not associated with submitted orders?

Open
#307 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feedback
Dominant language
C#
Stars
7
Forks
5
PR merge metrics
No merged PRs in 30d

Description

It seems the Purchasing system can inappropriately retain drafts of purchase requests. I'm guessing it's taking some sort of snapshots of work in progress, which of course is a great feature, but it's not "smart" enough to realize that some snapshots are later superseded by successfully-submitted orders. Here's a basic flow of what I mean:

I'm creating an order. It might take me 10-12 minutes to do so since I get interrupted and distracted during the process.
At some point during the order creation, the backup/snapshot of that work in progress is taken.
I eventually get around to finishing the order and it is successfully submitted.
Later, I go in to create a new order.
The system informs me that I was working on a form, and asks if I'd like to load it back up. When loaded, I see that it's a draft of the same order I had already successfully submitted. I'll then be nagged every time I attempt to create a new order, until "draft" is opened and canceled.

Basically, the draft/snapshot is not being properly associated with the successfully-submitted order- or, if it is, the system should be be discarding the draft data upon successful order creation.

Charles F Sievers III on May 30, 2013 12:07 PM (2 comments) Public permalink

Votes: 1
Author: jsylvest
Voters: jsylvest

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the described flow: create an order, allow a work-in-progress snapshot, submit the order, then begin another order and load the offered draft. Trace how snapshots are associated with submitted orders and define done as preventing the submitted order from reappearing as an active draft.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.