BCStudentSoftwareDevTeam / BCStudentSoftwareDevTeam/urcpp
Maximum total budget for a proposal changes from year to year
- Linguagem predominante
- HTML
- Estrelas
- 0
- Forks
- 0
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Descrição
Faculty stipends (which is solved by PR #183) brings about another issue, which is there is a warning hard-coded into the end of the proposal form which notifies the user that their proposal is over a certain amount: https://github.com/BCStudentSoftwareDevTeam/urcpp/blob/development/api/templates/pages/budget.html#L133
This number should be dynamic, which means it needs to be programmable in the Set Parameters page.
However, the current number ($8300) was derived from a $5300 faculty stipend (now wrong) + $3000 max budget for everything else (which may also change in the future). Worse yet, this doesn't take into consideration the fact that two or more faculty could be on a proposal, which would make the budget: 5300 + 5300 + 3000.
So, this needs reworked so that faculty stipends are treated separately from the other budget calculations when this warning is displayed. In reality, it should only be a check on the $3000 budget for everything else, and a separate check on the stipend based on the number of faculty on the proposal.
Both the stipend and the "everything else budgets" should be set in the Set Parameters page so they can change each year.
You'll also want to check the impact of this on previous years (i.e., fix the production data so the value is in there).
Guia de contribuição
Nenhum guia de contribuição indexado para este repositório
Direção de pesquisa
Comece em api/templates/pages/budget.html#L133 e rastreie como o formulário de proposta obtém seu valor de aviso atual. Em seguida, inspecione a página Set Parameters e os dados de produção de anos anteriores para identificar onde os valores de stipend e de outros orçamentos devem ficar. Está concluído quando ambos os valores forem configuráveis, o aviso os verificar separadamente para vários membros do Faculty e os dados dos anos anteriores continuarem preenchidos.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- html
- Domínio
- backend, web-dev
- Tipo de issue
- Funcionalidade
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Status de atividade
- Estagnada
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 45/100