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

Improve message formatting #67

Open
donlelef opened this issue Sep 9, 2021 · 4 comments
Open

Improve message formatting #67

donlelef opened this issue Sep 9, 2021 · 4 comments

Comments

@donlelef
Copy link
Member

donlelef commented Sep 9, 2021

Currently, when I ask for a report of my work, the following message is returned.

You worked 4.00d in 01 September 2021 - 01 October 2021
- brand: 0.25d
- sales: 2.00d
- marketing: 0.75d 

This may be improved in several ways, for instance by:

  • Rephrasing the first sentence, e.g. "Between 01 September 2021 and 01 October 2021, you worked 4 days (32 hours)",

Summary is calculated in ReportSummaryService

@khaelys khaelys removed their assignment Oct 6, 2021
@hphan9
Copy link
Contributor

hphan9 commented Oct 17, 2021

Hi team, I would like to work on this issue.
I have some questions and I hope you can help me answer them.
What is the best way to contact you?

@khaelys
Copy link
Collaborator

khaelys commented Oct 18, 2021

Hi @hphan9, thank you for reaching us.

You can join this temporary workspace on slack and ask questions on the clockify-bot channel. If your questions are about this issue, just write it down here.

@hphan9
Copy link
Contributor

hphan9 commented Oct 24, 2021

Hi @khaelys , I think to improve message formatting, I will edit the Clockify.ClockifyMessageSource.resx in Common/Resources folder. Is it the right approach? Thank you, and I am looking forward to hearing from you?

@khaelys
Copy link
Collaborator

khaelys commented Oct 25, 2021

Yeah, you need to edit ClockifyMessageSource.resx and the ReportSummaryService class 🍡

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

Successfully merging a pull request may close this issue.

3 participants