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

Old field values shown in the Issue Navigator for custom fields unavailable according to the Custom Field's context

XMLWordPrintable

    • 6.02
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 28 May 2018

      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 – 28 May 2018 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

      Steps:
      1. Create two projects A and B.
      2. Create a custom field CF1 and set its context to the "Global Context" (All issue types and projects."
      3. Create an issue "TestIssue" in project A with a value for custom field CF1
      4. Edit the context for custom field CF1 so it only applies to project B
      5. Search for all issues in the issue navigator in Details View and add a column for CF1 to the search results.
      6. [BUG] The value stored for the "TestIssue" in project A in step 3 is still shown.

      Expected behaviour:

      • The value should be "hidden" because of the new context restrictions specified in step 4.

      Workaround:

      • Hide the field via a Field Configuration / Field Configuration Scheme and apply this to project A

              Unassigned Unassigned
              ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: