As a schema admin I want to be able to define multiple language strings for field sets/reasons for issue to support defining a single schema that works globally.
As a schema admin I want to be able to define a logical order for the field sets - because in different languages the alphabetical approach we take currently will see the order of them change.
|
Practical use of functionality?
Define translations for the "For Action" reason for issue. |
|
|
What is the impact of not doing this?
Multiple schema have to be configured per language, increasing implementation and maintenance overheads. |