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

[PROD] Problem with the percentage display in the downloaded PDF #1067

Open
mpawlowski85 opened this issue Jan 30, 2019 · 4 comments
Open

[PROD] Problem with the percentage display in the downloaded PDF #1067

mpawlowski85 opened this issue Jan 30, 2019 · 4 comments
Assignees

Comments

@mpawlowski85
Copy link

mpawlowski85 commented Jan 30, 2019

There is an issue with the display of percentage progress in the downloaded pdf (Annex C Part 2). Please see the attachment. The numbers displayed in the system are correct, only the download is incorrect.

In the download - the percentages are multiplied by 100 (it should show 87 not 8700).

Annex C part 2.pdf

image

@mpawlowski85 mpawlowski85 changed the title Problem with the percentage display in the downloaded PDF [PROD] Problem with the percentage display in the downloaded PDF Jan 30, 2019
@brandinalexander
Copy link

@mpawlowski85 - Should the Progress Report display the percentages to the hundredths place?
ie: (87.00% OR 87%) - Thanks for clarifying.

@n1207n
Copy link
Contributor

n1207n commented Jan 30, 2019

I would delegate this to @dfryta, since he dealt with export features for the majority of time. I can do image building and deployment to PRP dev once this is resolved. I may have to discuss with Rob on deploying to production.

@mpawlowski85
Copy link
Author

mpawlowski85 commented Jan 31, 2019

@brandinalexander we will keep the same display as on the front end - so we should do 2 decimal places.

I have added Darek to the mix.
Thanks @n1207n - @robertavram can support on the deployment to production.

@chachra chachra added the Ready label Mar 6, 2019
@chachra
Copy link
Contributor

chachra commented Mar 6, 2019

This should be worked in right @mpawlowski85

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

No branches or pull requests

5 participants