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

iCalendar does not find date field with global context

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • 9.11.0
    • 8.20.0, 8.22.0, 9.4.0
    • REST API
    • 8.2
    • 5
    • Severity 2 - Major
    • 2
    • Hide
      Atlassian Update – 01 Aug 2023

      Dear Customers,

      We're happy to announce that this issue is fixed in 9.11 release. Learn more about the releases

      Before 9.11 the iCalendar plugin was not finding the date fields within implicit global context.

      As of Jira 9.11 the iCalendar plugin correctly returns all date fields that match the context of the given query (in most cases it is based on project query). If project in the query falls into implicit global context of the date field, that field is returned as an option by the iCalendar plugin.

      Best regards
      Jira DC Software Engineer

      Show
      Atlassian Update – 01 Aug 2023 Dear Customers, We're happy to announce that this issue is fixed in 9.11 release. Learn more about the releases Before 9.11 the iCalendar plugin was not finding the date fields within implicit global context. As of Jira 9.11 the iCalendar plugin correctly returns all date fields that match the context of the given query (in most cases it is based on project query). If project in the query falls into implicit global context of the date field, that field is returned as an option by the iCalendar plugin. Best regards Jira DC Software Engineer

      Issue Summary

      iCalendar app does not retrieve date field if field has multiple contexts and project is not specified in one of the non-global contexts

      This is reproducible on Data Center: (yes)

      Steps to Reproduce

      1. Create date field with Global context
      2. Create second context specifying project A
      3. Run ical REST call to retrieve all fields for project B 
        http://<baseurl>/rest/ical/1.0/ical/config/fields?jql=project=PROJECTB&useExpandedFieldRetrieval=true

      Expected Results

      New field is listed for project B

      Actual Results

      New field is only listed if you search for Project A's fields

      Workaround

      Include project B in a context explicitly or remove other contexts besides the global context

              b6cf9181bff6 Krystian M
              malmeida Marcus Silveira
              Votes:
              2 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: