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

Default value not displayed in "Select List" field with two contexts

XMLWordPrintable

    • 3.1
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 16 November 2017

      Hi everyone,

      The issue has not collected enough votes, watches, comments or support cases during it's lifetime. In this sense overal interest in the reported problem is low.
      Jira team is focusing on bigger and more impactful issues at the moment and we are not likely to look at the current bug soon. Therefore I'm resolving the issue as Timed Out.

      Atlassian will continue to watch issue for the further updates, so please don't hesitate to share your feedback in the issue comments.

      Cheers,
      Ignat Alexeyenko
      Jira bugmaster.

      Show
      Atlassian Update – 16 November 2017 Hi everyone, The issue has not collected enough votes, watches, comments or support cases during it's lifetime. In this sense overal interest in the reported problem is low. Jira team is focusing on bigger and more impactful issues at the moment and we are not likely to look at the current bug soon. Therefore I'm resolving the issue as Timed Out . Atlassian will continue to watch issue for the further updates, so please don't hesitate to share your feedback in the issue comments. Cheers, Ignat Alexeyenko Jira bugmaster.

      Hi,

      This seems to be a bug with JIRA: I added 2 "Select List" custom fields to the "Resolve Issue" screen for a group of projects. For each field, I created two contexts, because one of the projects requires a different set of options. In both fields, I set default values for the second context, but the problem is that the default value is not automatically selected in the "Resolve Issue" screen.

      The funny thing is that I have another "Select List" field in the same screen; this field is configured only with the default context, and also has a default value set, which is automatically selected when I enter the screen. Looks like the issue is present only when a custom field has more than one context.

      Please take a look at the attached document, which contains screenshots describing the issue with more detail. Have you ever detected this behavior? Is this something that might have been solved in newer versions of JIRA? This turned to be a little critical for me, because I was working on a request to set default values for the two fields described above (as the easiest approach), and it's getting more difficult than normal.

      Thanks in advance for your comments,
      GERMAN

              Unassigned Unassigned
              7d3a3ad782f5 German Rodriguez
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: