[jboss-jira] [JBoss JIRA] (DROOLS-2063) request to improve error message when failed to upload spreadsheet

[Michael Anstis (JIRA)]

     [ https://issues.jboss.org/browse/DROOLS-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Anstis moved GUVNOR-2474 to DROOLS-2063:
------------------------------------------------

              Project: Drools  (was: Guvnor)
                  Key: DROOLS-2063  (was: GUVNOR-2474)
             Workflow: GIT Pull Request workflow   (was: classic default workflow)
          Component/s: XLS Decision Table Editor
                           (was: XLS Decision Tables)
    Affects Version/s: 6.3.0.Final
                           (was: drools_6.3.0.Final)


> request to improve error message when failed to upload spreadsheet
> ------------------------------------------------------------------
>
>                 Key: DROOLS-2063
>                 URL: https://issues.jboss.org/browse/DROOLS-2063
>             Project: Drools
>          Issue Type: Enhancement
>          Components: XLS Decision Table Editor
>    Affects Versions: 6.3.0.Final
>         Environment: BRMS 6.2.x
>            Reporter: Hiroko Miura
>            Priority: Minor
>         Attachments: errorWhenUploadingSpreadsheet.png
>
>
> 1. Proposed title of this feature request
> Request to improve error message when uploading spreadsheet as multi-bytes name
> 2. Who is the customer behind the request?
> Account: name and acct #
> Fujitsu Systems East Limited(acct#5441134)
> TAM customer: no
> SRM customer: no
> Strategic: no
> 3. What is the nature and description of the request?
> This is relevant to BZ#1320011.
> In this issue, URL encoded Japanese asset name is shown in this error message,
> which it is not user friendly and a bit hard to recognize problematic asset immediately.
> Customer requests us to show human-readable asset name in such error message instead of URL encoded one.
> 4. Why does the customer need this? (List the business requirements here)
> As stated above, error message is not user friendly and bit hard to recognize problematic asset immediately.
> 5. How would the customer like to achieve this? (List the functional requirements here)
> Please show human-readable asset name.
> 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
> check improved error message
> 7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
> No
> 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
> No
> 9. Is the sales team involved in this request and do they have any additional input?
> No
> 10. List any affected packages or components.
> N/A
> 11. Would the customer be able to assist in testing this functionality if implemented?
> Yes



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)