Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #7517 PUT /milestones/:id/content throw error 500
    Actions
    Infos
    #7517
    Laurent Delaigue (ldelaigue)
    2014-10-10 13:17
    2014-10-09 11:47
    7523
    Details
    PUT /milestones/:id/content throw error 500
    I upgraded to Tuleap 7.5.99.49 and I now get an exception when trying to move an Epic from a product to a release.
    It used to work, I don't know exactly in which version it was broken.

    PUT /api/v1/milestones/329/content
    body:
    [328]
    __________
    response:
    HTTP/1.1 500 Internal Server Error
    body:
    {
    "error": {
    "code": 500,
    "message": "Internal Server Error: Les champs ne sont pas valides"
    },
    "debug": {
    "source": "NewChangesetCreatorBase.class.php:185 at call stage",
    "stages": {
    "success": [
    "get",
    "route",
    "negotiate",
    "authenticate",
    "validate"
    ],
    "failure": [
    "call",
    "message"
    ]
    }
    }
    }
    API
    development
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    New
    Empty
    Attachments
    Artifact links
    Empty
    By Laurent Delaigue (ldelaigue)
    (276 kB)
    agile_dashboard_template_3lvl.xml
    Agile configuration with 3 levels
    References
    Referenced by request #7517

    Other

    gerrit #3115
    Display settings

    Follow-ups

    User avatar
    Laurent Delaigue (ldelaigue)2014-10-10 13:17
    Thank you guys,

    I'll check on my side.
    As I understand it, reverting this change has a limited impact, since the problem solved only arised for artifacts created in a wrong way?

    In anycase, thank you very much for the effort put in all this.
    User avatar
    Laurent Delaigue (ldelaigue)2014-10-09 16:19
    >> Yes, I can add a follow-up comment to mielstone artifact 329 through the web UI
    >In your changeset, do you see any changes other than your comment?
    >And now that you modified it, do you see any difference in REST calls?

    1) In the changesets attached to artifact 329, there is nothing else thatn the comments I've added. Especially, no field value is set.
    2) Even after adding a follow-up comment to artifact 329, I still can't successfully assign an Epic to this milestone.

    >> What I meant in my previous comment was this : I am able to assign the Epic to milestone 329 through the web UI, even though it does not work through the REST API
    >Yes I do have the same behavior. The only difference on my side is that it works pretty fine through REST when the milestone is considered valid.

    Don't know what to answer. I believe you, but I can't have it to work here.
    I'm using a project configuration with 3 levels, the one provided by Patricia.
    User avatar
    Nicolas Terray (nterray)2014-10-09 15:34
    > Yes, I can add a follow-up comment to mielstone artifact 329 through the web UI
    In your changeset, do you see any changes other than your comment?
    And now that you modified it, do you see any difference in REST calls?

    > What I meant in my previous comment was this : I am able to assign the Epic to milestone 329 through the web UI, even though it does not work through the REST API

    Yes I do have the same behavior. The only difference on my side is that it works pretty fine through REST when the milestone is considered valid.
    User avatar
    Laurent Delaigue (ldelaigue)2014-10-09 15:23
    Hi Nicolas, sorry for being not accurate enough.

    - Yes, I can add a follow-up comment to mielstone artifact 329 through the web UI
    - What I meant in my previous comment was this : I am able to assign the Epic to milestone 329 through the web UI, even though it does not work through the REST API

    Hope this helps,

    Laurent
    User avatar
    Nicolas Terray (nterray)2014-10-09 15:16
    last edited by: Nicolas Terray (nterray) 2014-10-09 15:16
    Are you able to add a follow-up comment in the milestone artifact 329 through the web ui ?

    > Plus, I'm able to what the API refuses via the web site.
    Sorry I do not understand.
    User avatar
    Laurent Delaigue (ldelaigue)2014-10-09 15:01
    In fact, this problem appears on all the PUT /milestones/* routes, since I guess the same checks are performed everywhere.
    Plus, I'm able to what the API refuses via the web site.
    User avatar
    Laurent Delaigue (ldelaigue)2014-10-09 14:44
    Ah ok. I understand the solution you adopted, but in my case it looks like the milestone in which I try to plan items is valid. It has very few fields, and there are all filled in.
    Is there a way to know more precisely why Tuleap considers my sub-milestone is not valid?
    I don't see any message in the logs.
    User avatar
    Nicolas Terray (nterray)2014-10-09 14:28
    Hi Laurent,

    This has been introduced with the fix of request #7474: Error 500 when updating an artifact without status.

    Starting from this fix, it is not anymore possible to plan items in a milestone that has a required field which is not filled.
    User avatar
    Laurent Delaigue (ldelaigue)2014-10-09 12:02
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    • Reported in version changed from 7.5 to development