Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 18 Next »

On this page


Field Configuration

Before starting the field configuration, please follow the instructions for creating custom fields: Create a Custom Field

Step 1: Set a name and description

Provide a good name for the new custom field. Make it descriptive, concise, and easy to understand for others who will use it. Avoid using ambiguous or overly technical terms.

Step 2: Configure your custom field

The field allows you to choose from a pre-defined set of field sizes and calendar styles.

Step 3 (Optional): Dependent date

The value of the Calendar field can depend on other date fields, such as the due date, for example. If you wish to have such a dependency, you can configure it in the date field select.

This option does not work when used in Jira Service Management


Field view and edit


Related Use Cases

More use cases are coming soon. In the meantime, check out our other use cases.


Jira Service Management (JSM)

For the “dependent date” setting:

It is essential to populate or update the field initially through loading the issue view of the request, typically performed by an agent. Failure to do so will result in these fields remaining empty and consequently not displayed on the request view.

Before you can add a custom field for Jira Service Management (JSM) projects, you first need to setup the custom field

https://help-seibertmedia.atlassian.net/wiki/spaces/ACF/pages/11894823/Calendar#Field-Configuration

Then follow this guide to use the field in the request form or the portal view

Add Custom Fields to Jira Service Management


JQL expression

${fieldName}.calendar: Date

Example: a search for all issues with a calendar date on Christmas

"Calendar.Iso Datetime" = 2023-12-20T12:00:00Z

therefore, use the ISO-8601 date time format: YYYY-MM-DDTHH:MM:SS[.sss]Z


Data Structure (Automation)

To set the value via automation, you need the following object structure

Please note, that this will only work correctly, if you choose the manual date configuration.

{
  "calendar": "YYYY-MM-DD"
}

Example date: 2023-12-24 (for the 24th of December 2023)

  • No labels