Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-9872

Ranking issues only possible if customFieldId for Rank field is available

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Low
    • None
    • 6.3.2
    • None
    • Jira OnDemand

    Description

      Hi support,

      I have a problem with ranking issues inside a sprint. For that I am using the rest endpoint

      http://

      {HOST}

      /rest/greenhopper/latest/sprint/rank

      with the following params:

      { addToBacklog = false; idOrKeyBefore = "CDTPC-7"; idOrKeys = ( "CDTPC-1" ); sprintId = 187; }

      Unfortunately I get the following error:

      {"status-code":500,"stack-trace":"java.lang.NullPointerException\n\tat com.atlassian.greenhopper.web.rapid.sprint.SprintRankResource$1.call(SprintRankResource.java:113)\n\tat com.atlassian.greenhopper.web.rapid.sprint.SprintRankResource$1.call(SprintRankResource.java:78)\n\tat com.atlassian.greenhopper.web.util.RestCall.response(RestCall.java:48)\n\tat com.atlassian.greenhopper.web.AbstractResource.response(AbstractResource.java:60)\n\tat com.atlassian.greenhopper.web.rapid.sprint.SprintRankResource.updateSprintAndRank(SprintRankResource.java:77)\n\tat sun.reflect.GeneratedMethodAccessor5938.invoke(Unknown......

      I figured out that for making it work the "customFieldId"-parameter is missing. Is it really necessary to also add this parameter to the request? It would be nice if in case the id is not added the default field would be used. What is the best way to retrieve the right custom field id for the ranking field with rest?

      The question has been posted in the support forum, no answer yet

      https://answers.atlassian.com/questions/211566/greenhopper-rank-issue-via-rest-api

      Thanks!

      Attachments

        Activity

          People

            Unassigned Unassigned
            d403d295adf5 Talk About
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: