Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-60274

Provide disabled flag for /rest/api/2/customFieldOption/{id}

XMLWordPrintable

    • 9
    • 2
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Please add an attribute that communicates whether a custom field option is currently disabled.
      /rest/api/2/customFieldOption/

      {id}

      returns the option name/value. I would like to see something like the response shown here. 

      // 20160321144230
// http://localhost:8080/rest/api/2/customFieldOption/10104

{
  "self": "http://localhost:8080/rest/api/2/customFieldOption/10104",
  "value": "A"
  "disabled":true
}

      Relevant conversation at https://answers.atlassian.com/questions/242922/rest-api-for-custom-field-option-does-not-show-disabled-flag

            [JRASERVER-60274] Provide disabled flag for /rest/api/2/customFieldOption/{id}

            Debbie Buswell added a comment -

            Adding to Mr. Rathwell — can this be ported to 8.5?

            Debbie Buswell added a comment - Adding to Mr. Rathwell — can this be ported to 8.5?

            Mike Rathwell added a comment -

            Will this be backported to the 8.5 LTS release?

            Mike Rathwell added a comment - Will this be backported to the 8.5 LTS release?

            Torben Schumacher added a comment -

            tried to get the lowest value of a custom field, which is not disabled. Need a solution or a workaround for my script!

            Setting a value as default is not a solution, as the field is not mandatory until the ticket reaches a certain status.

            Torben Schumacher added a comment - tried to get the lowest value of a custom field, which is not disabled. Need a solution or a workaround for my script! Setting a value as default is not a solution, as the field is not mandatory until the ticket reaches a certain status.

            DORIAN KERSCH added a comment -

            this would be great...

            DORIAN KERSCH added a comment - this would be great...

            Chad Ullman added a comment -

            This has become an issue here at Delta Dental.  We have a custom tool that we use to upload test cases to Jira (we're using the Zephyr plugin for test case management).  As part of our upload process, we need to validate the input and so need to be able to ascertain that users are not using disabled values in certain fields.

            Chad Ullman added a comment - This has become an issue here at Delta Dental.  We have a custom tool that we use to upload test cases to Jira (we're using the Zephyr plugin for test case management).  As part of our upload process, we need to validate the input and so need to be able to ascertain that users are not using disabled values in certain fields.

            Kate Nevenchannaya added a comment -

            This is a major problem for Adobe when we integrate with other tools, e.g. via official/supported connectors. Some field values being disabled in Jira but still showing up on another end, result in confusion (when people see invalid field options) and failures to create issues from other tools.

            Jira is an essential part of our engineering toolchain that is rapidly growing, so priority of this problem is going up rapidly as well. 
            Please consider!

            Kate Nevenchannaya added a comment - This is a major problem for Adobe when we integrate with other tools, e.g. via official/supported connectors. Some field values being disabled in Jira but still showing up on another end, result in confusion (when people see invalid field options) and failures to create issues from other tools. Jira is an essential part of our engineering toolchain that is rapidly growing, so priority of this problem is going up rapidly as well.  Please consider!

            Deleted Account (Inactive) added a comment -

            Trying to integrate with Clarity for project names and this feature would make life a ton easier in syncing the valid lists. Second on adding the info to the createmeta response.

            Deleted Account (Inactive) added a comment - Trying to integrate with Clarity for project names and this feature would make life a ton easier in syncing the valid lists. Second on adding the info to the createmeta response.

            Pradeep Kumar added a comment -

            Expecting same functionality

            Pradeep Kumar added a comment - Expecting same functionality

            Ramesh Udari1 added a comment -

            Expecting same functionality with Core Jira REST API.

            Ramesh Udari1 added a comment - Expecting same functionality with Core Jira REST API.

            Adam Labus added a comment - - edited

            Hey guys,

            I added this functionality into my plugin Extender for JIRA

            Best regards
            AL

            Adam Labus added a comment - - edited Hey guys, I added this functionality into my plugin Extender for JIRA Best regards AL

              63999e271dab Pawel Cieszko
              a42d8cf64978 YesiS
              Votes:
              66 Vote for this issue
              Watchers:
              51 Start watching this issue

                Created:
                Updated:
                Resolved: