ucdavis / ucdavis/ipa-client-angular
BudgetView: buyout report/workflow
Open
Nobody has claimed this yet.
needs discussion
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
The workflow in pysch (and perhaps other departments follows:
- Replacement preference is indicated
- Relevant account/justification is provided (or staff have to hunt it down)
- Justification is deemed valid by grant analyst
- Replacement is approved by department chair (or others?)
- Relevant things are done in PPS (or elsewhere?) to move money to appropriate accounts.
- Replacement is confirmed.
Assisting with at least providing checkboxes for these steps would be helpful, and a report on the state of all buyouts would be helpful.
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.
Research direction
Start by locating the BudgetView entry point and any existing buyout-related views or workflow data. Review how departmental actions and reports are represented, then clarify the required checkbox states, approval roles, and report contents before defining completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angularjs, javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100