Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-52136

JIRA Issue custom field update a field failed

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: jira-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.103
      Jira plugin in Jenkins 3.0.0
      JIRA 7.3.5
    • Similar Issues:

      Description

      I want to update my field "Confidential Level" to new value "Class-A."

       

      Setting 1:

      Custom field ID=Confidential Level

      Field value=Class-A

      -----------------------------------

      message error:

      WARNING: jira rest client update fields error for issue SUPPORT-113
      java.util.concurrent.ExecutionException: RestClientException{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors={customfield_Confidential Level=Field 'customfield_Confidential Level' cannot be set. It is not on the appropriate screen, or unknown.}, errorMessages=[]}]}

       

      what means "It is not on the appropriate screen"???

      ------------------------------------------------------

      Setting 2:

      Custom field ID=10406    (I input the custom field ID to here)

      Field value=Class-A

      -----------------------------------

      message error:

      WARNING: jira rest client update fields error for issue SUPPORT-113
      java.util.concurrent.ExecutionException: RestClientException{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors={customfield_10406=Could not find valid 'id' or 'value' in the Parent Option object.}, errorMessages=[]}]}

       

      It seem it cannot find id or value.

      ------------------------------------------------------

        Attachments

          Activity

          Hide
          warden Radek Antoniuk added a comment -

          Scenario 1 - it looks like you have a problem with field/screen configuration and the API does not expose the custom field to Jenkins.

          Scenario 2 - that looks like a bug indeed, can you share your pipeline definition?

          Show
          warden Radek Antoniuk added a comment - Scenario 1 - it looks like you have a problem with field/screen configuration and the API does not expose the custom field to Jenkins. Scenario 2 - that looks like a bug indeed, can you share your pipeline definition?

            People

            • Assignee:
              Unassigned
              Reporter:
              liaopeng Liao Peng
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: