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

The Labels field appears to treat "not set" differently than other fields

    XMLWordPrintable

Details

    • 4.02
    • Severity 2 - Major
    • Hide
      Atlassian Update – 04 December 2017

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.

      Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 04 December 2017 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ignat Alexeyenko Jira Bugmaster

    Description

      (This is taken from a comment on another issue)

      The problem is actually with an empty value being handled in 2 different ways.

      Here is an empty value for labels:

      "labels": {
      "name": "labels",
      "value": [

      ],
      "type": "com.atlassian.jira.issue.label.Label"
    },

      Notice that the value is an empty array.

      Here is what happens when the description has an empty value:

          "description": {
      "name": "description",
      "type": "java.lang.String"
    },

      In this case, there is no value at all.

      I wrote a script assuming that the value field would be there for every field. In the case of "description" it is missing, but type is at the same location, so the type showed up in my output.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-23253 REST api does not have any specified behavior for returning issue fields that are empty

          • Low - Low priority issues
          • Closed

          Activity

            People

              Unassigned Unassigned
              jpendleton Justus Pendleton (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: