RY Report: Non latin propertie name

Description

Reproduce scenario:
Step 1:
Create requirement with intended ID, definition (any), and properties:

  • 作者

  • Автор

  • 著者

  • הכותב

Step 2
Create RY Report with selection requirement by key created in step 1.

Step 3
Save page

Expected result
Report with single requirement record is. displayed. Report record has properties named:
作者
Автор
著者
הכותב

Actual result
Propeties names are displayed in unicode codes.

Motivation

Using RY Yogi in international environment requires support latin property names in cyrillic, japaneese, chinese and etc. languages in reports and analysis documents.

Currently using non-latin requirement propertie(attribute) name causes string transformation to string of character codes (seems like UTF-like or HTML charcodes) in reports. (RY Report macro).

For example instead of cyrrilic Авторы string Авторы is displayed in RY Report.

Current workaround is to add "RY Property" macro with latin property name. But it greatly increases personnel requiements in local projects.

Environment

None

Observations

None

Activity

Show:
Alexander Luchkov
January 13, 2020, 11:50 AM

At glance seems like fixed. I’d like to try searching RQs by properties containing macrosses like “Handy status” containing UTF-8 chars, but it will be another story in my opinion.

Adrien Ragot (Play SQL / Requirement Yogi)
January 13, 2020, 8:55 AM

Hi Alexander,

I have delivered the correction. Feel free to reopen this ticket if it doesn't work as expected.

Best regards,
Adrien

Alexander Luchkov
January 6, 2020, 1:48 PM

Hello, Adrien. Yes, that's only RY Report macro behaviour.

>
As it was set by initial priority, resolving issue is matter of months
(actually up to 2), so no complaints about current release plan.

Many thanks for your response and best regards. Alexander Luchkov.

Adrien Ragot (Play SQL / Requirement Yogi)
January 6, 2020, 10:52 AM

Hi Alexander,

You are correct. If I have checked properly, it is only in the RY Report macro, is that correct too?

As it is a new feature, it is not a degradation of your previously-working environment, just an incompleteness of a new feature, so I'll add it to the next release but I won't accelerate the release cycle for this.

Best regards,
Adrien

Resolved

Assignee

Adrien Ragot (Play SQL / Requirement Yogi)

Reporter

Alexander Luchkov

Labels

None

Participants

None

Components

Fix versions

Affects versions

Priority

Matter of months