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

Basic filter fails with long value for Label field type exceeding 255 characters

    XMLWordPrintable

Details

    • 6.02
    • 1
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 06 November 2019

      Hi everyone,

      After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out.

      Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy.

      To see what the Jira team is currently working on and has recently delivered see the following dashboards:

      We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

      Thank you,

      Pawel Drygas,

      Jira Server Bugmaster

      Show
      Atlassian Update – 06 November 2019 Hi everyone, After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out . Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy . To see what the Jira team is currently working on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments. Thank you, Pawel Drygas, Jira Server Bugmaster

    Description

      The basic filter fails after 255 characters, with below error thrown:

      Error Messages

      Error Message in UI : "The JIRA server could not be contacted. This may be a temporary glitch or the server may be down."

      JIRA log error : 2014-03-18 09:27:02.977473500 Mar 18, 2014 9:27:02 AM org.apache.catalina.core.StandardWrapperValve invoke
      2014-03-18 09:27:02.977475500 SEVERE: Servlet.service() for servlet action threw exception
      2014-03-18 09:27:02.977476500 com.atlassian.jira.issue.customfields.impl.FieldValidationException: The label 'D*** E*** K** E*** D*** L*** M*** S*** B*** D*** k*** N*** S*** D*** L*** L*** B*** M*** D*** B*** N*** l*** N*** N*** N*** N*** L*** B*** M*** ' exceeds the maximum length for a single label of 255 characters.
      2014-03-18 09:27:02.977490500 at com.atlassian.jira.issue.customfields.impl.LabelsCFType.convertStringsToLabels(LabelsCFType.java:339)
      2014-03-18 09:27:02.977492500 at com.atlassian.jira.issue.customfields.impl.LabelsCFType.getValueFromCustomFieldParams(LabelsCFType.java:274)
      2014-03-18 09:27:02.977492500 at com.atlassian.jira.issue.customfields.impl.LabelsCFType.getValueFromCustomFieldParams(LabelsCFType.java:70)

      However this does not affect search query in advance mode.

      Steps to reproduce

      1. Create a custom field with type label i.e Client Name(Issue type association: Global (all issues))
      2. Associate to default screen
      3. Create multiple issues with different Client Names.
        • Sample values for the custom field: APM, APMT, AXA, BV, BV2, Barrick, BarrickAction, Bruss, Brussels, BureauVeritas, Butterfield, DEKRA, DP, DWTC, Danagas, DekraCert, DekraEurope, Dow, Dubai, DubaiPetroleum, EMCOR, Emcor, EmcorTest, FoodAlert, KEB, KEBS, KERRY, Kephis, Kerry, LL, LanguageLine, Lehnkering, Libert, Lockton, Lockton_Staging, MCB, Mactwin, Maersk, NR, NR_, NR_Phase_1, NR_Phase_2, NR_Phase_3, NR_Phase_4, NR_Staging, NorthLanarkshire, Nr, SFI, SOCOTEC, Socotec, Struers, Svitzer, kerry, locktonstaging, MCI, HAL, CRC
      4. Search for issues in issue navigator in advance mode
        • Sample Query: "Client Name" in (APM, APMT, AXA, BV, BV2, Barrick, BarrickAction, Bruss, Brussels, BureauVeritas, Butterfield, DEKRA, DP, DWTC, Danagas, DekraCert, DekraEurope, Dow, Dubai, DubaiPetroleum, EMCOR, Emcor, EmcorTest, FoodAlert, KEB, KEBS, KERRY, Kephis, Kerry, LL, LanguageLine, Lehnkering, Libert, Lockton, Lockton_Staging, MCB, Mactwin, Maersk, NR, NR_, NR_Phase_1, NR_Phase_2, NR_Phase_3, NR_Phase_4, NR_Staging, NorthLanarkshire, Nr, SFI, SOCOTEC, Socotec, Struers, Svitzer, kerry, locktonstaging, MCI, HAL)
      5. Switch to basic mode search
      6. Add client name CRC

      Workaround

      Use query in advance search mode.

      Attachments

        Activity

          People

            Unassigned Unassigned
            namir Nursihah Amir (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: