I want the custom field to be shown on Create Event and Edit Event dialogs
For a custom field to be shown on the Create Event and Edit Event dialogs, it has to be added to Jira dates source configuration, first.
To do that,
open a calendar configuration
click to edit the source configuration
scroll down to Issue fields
Insert the field you want to appear on the dialogs
make sure that the checkbox “i“ is ticked so the field appears on the dialogs
click Save button
Once the field is added, it shall appear on the Create Event and Edit Event dialogs.
I am not able to create or edit an event because of the error
You might encounter the next error when creating or editing a Jira dates based event:
Very often, the reason why a user is not able to create an event with a new Jira issue creation or edit an existing event is, simply, because the Jira field that the event is based on, is missing from a project’s screen.
As, in example above, the Jira field Due date is not present on the Default and Bug screens of the project “Cloud Silver (CS)”.
In order to avoid the error and to be able to create or edit an event, the Due date field shall be added to the project’s screens.
To do that an admin would have to go to the project settings and edit the project’s screens, as shown below.
There might be a case that the appropriate Jira field is present on Create screen but missing from Edit screen. Therefore, should the error appear, and admin has to check the project’s screens carefully and make the required changes.
Another reason for not being able to create or edit an event based on Jira dates source is a missing required permission. Please see the table below of possible cases.
The permissions to verify
If not granted this permission, you'll not be able to create an event with a new Jira issue creation.
This permission is required in order to set a due date for the issue. If not granted the permission, you'll not be able to create an event based on the field “Due date”.
Without being granted the permission, you’ll not be able to edit an event by assigning the issue the event is based to another user.
The permission is required in order to be able to assign issue to yourself. If not granted the permission, you'll not be able to edit an event and change the assignee to yourself, even though, you are granted the permission "Assign Issues".
The permission is required in order to be able to edit the events by changing the dates, assignee, etc.
Without being granted this permission, you'll not be able to edit a reporter for issue the event is based on.
Why I don't see the created calendar, in a project context view?
Most likely, you don't see the created calendar, in a project context view, because it doesn't contain any sources associated with the given project.
When creating a Jira dates event I would like to be able to provide the value for the field Component
The fields that appear as non-editable fields, as the field Component, for instance, on Create/Edit Event dialog, can be filled in during event creation and editing. Please refer to Create and Edit Links on dialogs to find out how this can be achieved.
What is the difference between Issue fields, Event fields, Report fields and Aggregated fields?
Issue fields- are the attributes of Jira issues. These are the standard and custom Jira fields. Examples: assignee, reporter, priority, due date, etc. The issue fields are used in source configuration, including conditional colors, and report field configuration.
Event fields- are the attributes of custom events such as Meetings, for instance. Examples: event user(s), event reporter, event summary, event description, etc. The event fields are used in source configuration, including conditional colors, and report field configuration.
The event fields cannot be added to Jira dates source configuration.
Report fields- are the fields that can be added to report field configuration. They include issue fields and event fields. In addition, there are unique report fields that can be used specifically in reports such as event source, day, week, and month.
Aggregated fields- are the fields that have been created specifically for the application to aggregate the value for two different event types, Jira dates and custom. Examples: Σ Summary, Σ Description, Σ Reporter. Such fields can be used in reports but not in source configuration.
In addition, there are aggregated field for parent, epic and time tracking fields such as Σ Parent, Σ Epic, Σ Epic Name, Σ Original Estimate, Σ Remaining Estimate and Σ Time Spent.
Such fields can be used in reports and in source configuration.
The conditional color that includes the function “endOfWeek()“ is not working properly
You might experience the next issue when the configured conditional color that includes the function “endOfWeek()“ is not working correctly.
For instance, as an app user, in User settings, I’ve configured my week to start on Monday:
Then, in source configuration, I’ve configured the conditional color: Due date <= endOfWeek() → red.
Although, the configured conditional color is not applied to the event that is based on issue that has a due date that falls on Saturday of the current week.
The root cause of the issue is laying in Jira’s behavior as, in Jira, week starts on Sunday.