Knowledge Base > Configuration FAQ

Configuration FAQ

How to create issues of different types in JIRA, including Sub-tasks

To create issues with a non-default issue type, map Issue Type to a custom text field and then populate the field with the desired issue type for each task:

Map issue type to field.

Populate the issue type column.

When createing Sub-tasks, please also make sure that the parent tasks of these tasks are or will be associated with JIRA issues (e.g. will not be skipped during synchronisation) because the new sub-tasks will need a parent.

How to make Ceptah Bridge skip some tasks during synchronisation

To skip a particular task, enter 'skip' in the field containing issue key (Text10 by default).

No differences found during synchronisation

If you start synchronisation, but no changes are coming up in the list, most likely this is because you have not specified resources for the tasks in your project. By default, such tasks are skipped during synchronisation. The number of skipped tasks is displayed in the left bottom corner of the synchronisation window.

To solve the problem, either assign resources to the tasks or change the synchronisation settings.

How to leave Security Level, Components, Fix Versions or Affects Versions blank when a default value is specified

When an issue is created or synchronized and the mapped field in MS Project is blank, the JIRA field is set to the default value specified in the mappings.

To make the JIRA field empty regardless of the default settings, enter '(none)' in the respective column in MS Project.

How to map MS Project Server Enterprise fields

The Enterprise Fields are supported, but they are not available in the drop-down lists. Please enter the field names manually where required.