Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vector Input for Tax Rates #8

Open
5 of 10 tasks
HCBINL opened this issue Sep 15, 2020 · 1 comment
Open
5 of 10 tasks

Vector Input for Tax Rates #8

HCBINL opened this issue Sep 15, 2020 · 1 comment
Labels
priority-normal task New feature or request

Comments

@HCBINL
Copy link

HCBINL commented Sep 15, 2020


Issue Description

Is your feature request related to a problem? Please describe.
Depending on the level of corporate income or other factors, projects could experience different tax rates for the same project over different years. As such, it would be beneficial to have the ability to input tax rates in a vector format, similarly to alpha and driver.

Describe the solution you'd like
Vector input for tax rates.

Describe alternatives you've considered
None (very new user)


For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

  • 1. Is it tagged with a type: defect or task?
  • 2. Is it tagged with a priority: critical, normal or minor?
  • 3. If it will impact requirements or requirements tests, is it tagged with requirements?
  • 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
  • 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

  • 1. If the issue is a defect, is the defect fixed?
  • 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
  • 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
  • 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
  • 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
@HCBINL HCBINL added the task New feature or request label Sep 15, 2020
@alfoa
Copy link
Collaborator

alfoa commented Sep 15, 2020

@HCBINL thank you for your feedback

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority-normal task New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants