search

18F / ogp-payroll

Front end for the OGP Payroll Reporting prototype project
Other
3 stars 3 forks source link

Prime Setup: Update setup flow to allow primes to easily review and edit contract details for subs #49

Open LarryBafundo opened 8 years ago

LarryBafundo commented 8 years ago

As a prime contractor, I want to assign subcontractors to a contract # and provide relevant contract details so they can start submitting certified payroll.

Contact details to include:

-contract # -project location & name -period of performance -approved work classifications, wage determinations, and fringe benefits

maya commented 8 years ago

For reference, this is how github adds people and teams to a repo.

screen shot 2016-04-25 at 10 16 15 am screen shot 2016-04-25 at 10 15 47 am
LarryBafundo commented 8 years ago

update per team meeting on April 25:

we are planning on showing this view with data already populated, although fully editable. while our research and report of findings will explore plausible ways in which this information could be populated, or manually entered, how the data is populated is not important to show at this time.

maya commented 8 years ago

Tasks

hbillings commented 8 years ago

PR #63 shows the view-only version of this.

LarryBafundo commented 8 years ago

updated the issue description per our discussion earlier today. for the current sprint, let's just focus on showing what this view looks like and we'll worry about the mechanics of how it works later.

LarryBafundo commented 8 years ago

@hbillings a couple of edits to your current iteration at https://pages-staging.18f.gov/ogp-payroll/create-new-contract/#.

1) can we show how the prime contractor field would be auto-populated, based on the user's login? 2) can we add a contract start and end date? 3) probably doesn't apply to this view, but we also want to allow for removing subs from a contract (for when their scope of work ends) 4) for the work classification section, add a county field instead of city and state, since wage determinations are associated by county. 5) users should be able to enter in the work classification from the contract and based on their location, we should be able to auto-populate some of the supporting detail so they're not burdened with excessive manual entry. however, it's important for users to be able to enter in the wages and fringe benefits that are stated in the contract, not what's pulled from WDOL. we may want to auto-populate that data, but require users to confirm that they're correct.