[ 
https://issues.apache.org/jira/browse/YETUS-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470558#comment-15470558
 ] 

Allen Wittenauer commented on YETUS-446:
----------------------------------------

I think when errorMessages actually context text we should provide that as 
output perhaps in addition to our own.  e.g.,

{code}
JIRA returns HTTP error 400: Bad Request. Aborting.
- Please make sure the specified projects are correct.
- The value 'yahoo' does not exist for the field 'project'.
- The value '56' does not exist for the field 'fixVersion'.
{code}

Or something like that perhaps?

> releasedocmaker not handling 0 version in a range correctly?
> ------------------------------------------------------------
>
>                 Key: YETUS-446
>                 URL: https://issues.apache.org/jira/browse/YETUS-446
>             Project: Yetus
>          Issue Type: Bug
>          Components: Release Doc Maker
>    Affects Versions: 0.4.0
>            Reporter: Allen Wittenauer
>            Assignee: Ajay Yadava
>         Attachments: YETUS-446.00.patch
>
>
> Playing around this morning, I seem to have hit an interesting bug.
> {code}
> releasedocmaker --project FALCON --outputdir FALCON --projecttitle 'Apache 
> Falcon' --version 0 --version 1 --range --index --license
> {code}
> results in this URL getting generated:
> {code}
> https://issues.apache.org/jira/rest/api/2/search?jql=project+in+%28%27FALCON%27%29+and++++++++++++++++fixVersion+in+%28%270.0%27%29+and++++++++++++++++resolution+%3D+Fixed&startAt=0&maxResults=100
> {code}
> A completely valid URL.  However,  RDM reports on the screen:
> {code}
> JIRA returns HTTP error 400: Bad Request. Aborting.
> Please make sure the specified projects are correct.
> {code}
>  whereas JIRA spits back
> {code}
> {"errorMessages":["The value '0.0' does not exist for the field 
> 'fixVersion'."],"errors":{}}
> {code}
> So somewhere we are generating an invalid version and not verifying it with 
> JIRA. Additionally, our error message is wrong which isn't going to help the 
> user at all.  :(



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to