[ANALYTICS-306] Year displayed with a comma (e.g. 2,021 instead of 2021) Created: 15/Feb/21  Updated: 30/Jan/23  Resolved: 30/Jan/23

Status: Closed
Project: Analytics
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Julie Legendre Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2021-02-15-14-17-04-341.png    
Issue Links:
relation
is related to MGNLUI-6118 Type Long in JCR should not have commas Closed
Template:
Acceptance criteria:
[ ]* Investigate if we can disable comma but please consider for a thousand or million the comma will help. In case we can't not find any programmatically to detect year, we need to propose a manual amchart configuration for user in wiki
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: Analytics later
Story Points: 5
Team: AuthorX

 Description   

Steps to reproduce

This may be just due to the dummy data supplied but just in case, I'm creating this ticket. In the JSON path evaluator, the years are displayed correctly.

  1.  Add a widget for a json data supplier
  2.  Select year in the Y axis

..

Expected results

Year displays without a comma in X and Y axes.

Actual results

Year displays with a comma in the Y axis.

 

 



 Comments   
Comment by Šimon Demočko [ 24/Feb/21 ]

BTW I don't think a year should be Long typed. It's doubtful Magnolia would outlive a year of Integer.MAX_VALUE (2,147,483,647) and by that time the commas would actually become quite useful.

Comment by Laura Delnevo [ 30/Jan/23 ]

Hello, 

This ticket is now marked as closed due to one of the following reasons: 

  • A long period of inactivity 
  • Uses an old or Beta version of an application, module, or framework that we no longer support 
  • The issue is no longer reproducible or has been fixed in later versions 

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you. 

Thank you, 

The Magnolia Team

Generated at Sun Feb 11 23:17:36 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.