Choosing a Purchase Request as a 'Favorite' for easy access with Blankets
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue names no files, tests, or entry points. Start by locating the blanket-agreement and purchase-request completion workflows, then determine where requestors access completed requests. Done should define how a purchase request remains easy to find until its final line item is received, including the proposed favorite or persistent-tab behavior.
Written by the indexing model from the issue text.
Description
We have several blanket agreements with vendors and it would be really nice to have easy access to particular agreements so that we can find them easier throughout the year. An example: ADDA-EH25WB1. We will upload invoices and recieve all year long and it would be helpful for Requestors (who normally don't know much about purchasing and therefore tend to forget functionality) to have it stay "open" or under a tab that stays live until the very last line item is received. For now, this requestor will have to write down the OPP request number and keep it handy each month so that he can look it up and upload the invoice since it's deemed 'completed' when it's not.
....Oh, just saw that someone else had this same idea. Well, it was a good one apparently.
Melissa E Sullivan on September 10, 2013 11:11 (2 comments) Public permalink
Votes: 1
Author: jsylvest
Voters: jsylvest
- Dominant language
- C#
- Stars
- 7
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ucdavis/Purchasing
-
remove elmah Open
Difficulty 1/5 Under an hour Newbie friendliness 68/100
ucdavis/Purchasing#436 ·
-
feedback
Difficulty 3/5 1-2 days Newbie friendliness 55/100
ucdavis/Purchasing#659 ·
-
feedback
Difficulty 4/5 3-5 days Newbie friendliness 35/100
ucdavis/Purchasing#652 ·
-
feedback
Difficulty 5/5 Over a week Newbie friendliness 25/100
ucdavis/Purchasing#633 ·
-
feedback
Difficulty 4/5 3-5 days Newbie friendliness 25/100
ucdavis/Purchasing#632 ·
All issues in ucdavis/Purchasing
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·
-
area/docs-content Bug pulumi/docs
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
-
agentic-workflows untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100