Jira's custom date field doesn't appear when creating TC event if the custom field context is restricted to a specific issue type

Issue Summary

Confluence allows you to insert Jira issue dates (using default or custom fields) into the Team Calendar by creating an event.

However, if your custom field is configured so that the issue types associated with the default configuration of the custom field is not to all issue types available, then the custom field won't appear in the TC "Create event" dialog.

This only happens if the JQL/filter you use selects more than one project. If you select the projects individually, it works just fine.

Environment

• Confluence 6.6.13, 6.14.0
• Jira 7.6.7, 7.7.2, 8.2.1
• Team Calendar 6.0.27

Steps to Reproduce

1. Create an applink between Jira and Confluence.
2. In Jira, create two projects.
3. Create a custom date field, then associate it with all screens in the two projects.
4. Configure the custom field so that the applicable issue types are just set to one of them (i.e. "Task").
   • 
5. Save the config and create a sample issue (type "Task") in Jira.
6. In Confluence, create a simple Jira Issue Macro on a page to enable OAuth for your user.
7. Create a calendar and try to create an event of type "Jira Issue Dates".
8. Select a single project and you can see the custom field "Release Date" appear.
   • 
   • 
9. Now insert a JQL so that it includes two projects.

   project in ("Project One", "Project Two")

Expected Results

The custom field "Release Date" should appear as well.

Actual Results

The custom field "Release Date" doesn't appear when the JQL includes two projects. If you go back to just one project, it works fine.

Note

Confluence makes a REST call to obtain the date fields to display in the dialog. For example:

• http://localhost:8093/conf614/rest/calendar-services/1.0/calendar/jira/c8294f2e-923d-34cf-a218-858f95e7e0d0/date-fields/jql.json?query=project+in+(%22Project+One%22%2C+%22Project+Two%22)

The API results don't include the custom field if two projects are in the JQL.

[
  {
    "customfield": false,
    "name": "Issue Due Date",
    "key": "duedate"
  },
  {
    "customfield": false,
    "name": "Version Due Date",
    "key": "versiondue"
  },
  {
    "customfield": false,
    "name": "Sprints",
    "key": "sprint"
  },
  {
    "customfield": false,
    "name": "Issue Created Date",
    "key": "created"
  },
  {
    "customfield": false,
    "name": "Issue Resolved Date",
    "key": "resolution"
  }
]

If I only choose a single project or perform the workaround below (with two projects), the custom field is returned.

[
 {
    "customfield": false,
    "name": "Issue Due Date",
    "key": "duedate"
  },
  {
    "customfield": false,
    "name": "Version Due Date",
    "key": "versiondue"
  },
  {
    "customfield": false,
    "name": "Sprints",
    "key": "sprint"
  },
  {
    "customfield": false,
    "name": "Issue Created Date",
    "key": "created"
  },
  {
    "customfield": false,
    "name": "Issue Resolved Date",
    "key": "resolution"
  },
  {
    "customfield": true,
    "name": "Release Date",
    "key": "customfield_10200"
  }
]

Workaround

1. Choose only one project in the TC event you're creating.
2. Change the applicable issue types for the custom field's "Default Configuration Scheme" so that it's set to "All issue types" and not specific ones.