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

Check/Review tock banners according to new guidance. #1546

Open
4 of 11 tasks
edwintorres opened this issue Feb 21, 2023 · 4 comments
Open
4 of 11 tasks

Check/Review tock banners according to new guidance. #1546

edwintorres opened this issue Feb 21, 2023 · 4 comments

Comments

@edwintorres
Copy link
Member

Point of contact on this issue
Who can we follow-up with if we have questions?
@kfoley-18F @sheelio

Billable?

  • Yes
  • No
    tock code:
    1109

Skills needed

  • Any human
  • Design
  • Content
  • Engineering
  • Acquisition
  • Product
  • Other

Timeline
Does this need to happen in the next two weeks?

  • Yes
  • No

How much time do you anticipate this work taking?
1-3 days

A description of the work

With the new Tock's guidance, the directions/content about how to tock inside the app could need to be checked/reviewed.

Acceptance Criteria

What does "done" look like?

The conclusion of this issue could be an update or not to the directions on tock.

@sheelio
Copy link

sheelio commented Feb 21, 2023

Hot take on this: I would love if we actually showed users how many hours a given project allocation + their 670 time resulted in, so they could then account for the rest of their time.

(That would also allow you to use the total hours / billable hours section at the bottom of your timecard which currently disappears if you have weekly allocation projects).

@melchoyce
Copy link
Member

Per the labels, would this be django, html, or js?

@edwintorres
Copy link
Member Author

The label content is on a field in the Admin panel, under Hours > Timecard Notes

@MelissaBraxton
Copy link

This requires admin access, so we're going to remove it from the TLC board. @kfoley-18F, @edwintorres and @cantsin will take this on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants