Ceptah Bridge > Operations guide > Settings > Project settings >
Basic Mappings
PreviousNext

  1. In order to change the basic Ceptah Bridge mappings, select Basic tab in the Project settings window.

  2. An explanation of the Basic Mappings tab is provided below.

    Field Description
    Issue Key
    Field

    Select the task field to store the linked issue key.

    If a task is linked to an issue, the field contains the Issue Key. If the field is blank, the task is not linked to an issue and a new issue will be created for the task during synchronisation.

    Import: The selected task field will be populated with the Key of the source issue.

    Sync (unlinked task): The selected task field will be populated with the Key of the created issue.

    Sync (linked task): The selected task field value will be used to find the linked issue.

    *Put SKIP into the field to ignore a task during synchronisation.

    Project
    Project Key Tick the option to map issue project by project key.
    Project Name Tick the option to map issue project by project name.
    Default

    Select the default project.

    Import: Has no effect.

    Sync (unlinked task): A new issue will be created in this project by default.

    Sync (linked task): See the help for the Field combo box.

    Field

    Select the task field to map to JIRA Project Key or Name.

    Import: The selected task field will be populated with the Project Key or Name of the source issue.

    Sync (unlinked task): If the selected field is not blank for the task, the new issue will be created in the respective project. Otherwise, the default Project will be used.

    Sync (linked task): The selected field will be set to the Project Key or Name of the linked issue if it is different from the default Project Key or Name.

    Summary
    Populate Epic Name Tick to set Epic Name to the same value as Summary if the issue is an Epic. The option has no effect during import or when synchronising a linked task and the direction is from JIRA to MS Project.
    Direction Button Press the button to change the direction of issue Summary synchronisation.
    Task name path

    Tick the option to use parent task names to generate issue Summaries during synchronisation.

    Import: The imported task name will be populated with the source issue Summary. The parent task names will be ignored.

    Sync (unlinked task): The names of the parent tasks delimited by the given separator and followed by the name of the synchronised task itself will be used as Summary for the new issue.

    Sync (linked task): The issue Summary will be set to the names of the parent tasks delimited by the given separator and followed by the name of the synchronised task itself.

    The option is not available if the synchronisation direction is from JIRA to MS Project.

    Separator Select a separator to use when generating issue Summaries using the “path” method.
    Skip first n parent tasks Enter the number of first top-level parent tasks to be excluded from the path.
    Task name

    Tick the option to map issue Summary to task Name.

    Import: The imported task Name will be populated with the source issue Summary.

    Sync (unlinked task): The new issue Summary will be populated with the task Name.

    Sync (linked task): The issue Summary will be set to the task Name or the task Name will be set to the issue Summary, depending on the direction of synchronisation.

    Another Field

    Tick the option to map issue Summary to a task field.

    Import: The selected task field will be populated with the source issue Summary.

    Sync (unlinked task): The new issue Summary will be populated with the value of the selected task field.

    Sync (linked task): The issue Summary will be set to the value of the selected task field or the selected task field will be set to the issue Summary, depending on the direction of synchronisation.

    Another Field (combo box) Select the task field to map to issue Summary.
    Issue Type
    Default

    Select the default Issue Type.

    Import: Has no effect.

    Sync (unlinked task): The Issue Type will be used by default when a new issue is created.

    Sync (linked task): See the help for the “Field” combo box.

    Field

    Select the task field to map to Issue Type.

    Import: The selected task field will be populated with the Type of the source issue.

    Sync (unlinked task): If the selected task field is not blank, the new issue will have the given Type. Otherwise, the default Issue Type will be used.

    Sync (linked task): The selected task field will be set to the Type of the linked issue if it is different from the default Issue Type.

    Priority Tick the option to enable Priority synchronisation.
    Direction Button Press the button to change the direction of issue Priority synchronisation.
    Default

    Select the default Priority.

    Import: Has no effect.

    Sync (unlinked task): The Priority will be used by default when a new issue is created.

    Sync (linked task): See the help for the “Field” combo box.

    Field

    Select the task field to map to issue Priority.

    Import: The selected task field will be populated with the Priority of the imported issue.

    Sync (unlinked task): If the selected task field is not blank, the new issue will be created with the given Priority. Otherwise, the default Priority will be used.

    Sync (linked task): If the synchronisation direction is from JIRA to MS Project, the selected task field will be set to the Priority of the linked issue if it is different from the default Priority.

    If the synchronisation direction is from MS Project to JIRA and the selected task field is not blank, the issue Priority will be set to the field value. If the field is empty, the defaut Priority will be used.

    Due Date Tick the option to enable Due Date synchronisation.
    Direction Button Press the button to change the direction of issue Due Date synchronisation.
    Finish

    Tick the option to map issue Due Date to task Finish.

    Import: The Finish task field will be populated with the source issue Due Date.

    Sync (unlinked task): The Due Date of the new issue will be populated with the task Finish.

    Sync (linked task): The issue Due Date will be set to the task Finish or the task Finish will be set to the issue Due Date, depending on the direction of synchronisation.

    Field

    Tick the option to map issue Due Date to a task field.

    Import: The selected task field will be populated with the source issue Due Date.

    Sync (unlinked task): The Due Date of the new issue will be populated with the value of the selected task field.

    Sync (linked task): The issue Due Date will be set to the value of the selected task field or the selected task field will be set to the issue Due Date, depending on the direction of synchronisation.

    Field (combo box) Select the task field to map to issue Due Date.
    Assignee Tick the option to enable Assignee synchronisation.
    Direction Button Press the button to change the direction of issue Assignee synchronisation.
    Resource Name

    Tick the option to map issue Assignee to task Resource Name.

    Import: The Resource Names task field will be populated with the source issue Assignee.

    Sync (unlinked task): The Assignee field of the new issue will be populated with the task Resource Names. The task should be allocated to one resource only.

    Sync (linked task): The issue Assignee will be set to the task Resource Names or the task Resource Names will be set to the issue Assignee, depending on the direction of synchronisation.

    Resource Field

    Tick the option to map issue Assignee to a task field.

    Import: The selected task field will be populated with the source issue Assignee.

    Sync (unlinked task): The Assignee field of the new issue will be populated with the selected task field.

    Sync (linked task): The issue Assignee will be set to the value of the selected task field or the selected task field will be set to the issue Assignee, depending on the direction of synchronisation.

    Resource Field (combo box) Select the task field to map to issue Assignee.
    Field

    Tick the option to map issue Assignee to task assignment by a resource field.

    The resource fields are not to be confused with task fields. Resource fields can be edited using the Resource Sheet view in MS Project.

    Import: The new task will be assigned to the resource that has the value of the selected field equal to the source issue Assignee.

    Sync (unlinked task): The Assignee field of the new issue will be populated with the value of the selected field for the resource the task is assigned to.

    Sync (linked task): If the synchronisation direction is from JIRA to MS Project, the task will be assigned to the resource that has the value of the selected field equal to the source issue Assignee.

    If the synchronisation direction is from MS Project to JIRA, the Assignee field of the issue will be set to the value of the selected field for the resource the task is assigned to.

    Field (combo box)

    Select the resource field to map to issue Assignee.

    The resource field is not to be confused with a task field.

    Do not create issue if no assignee Tick the option to skip issue creation for the tasks that do not produce a value for issue Assignee.
    Ignore non-work resources Tick the option to ignore all assignments to cost and material resources. These assignments will be preserved during synchronisation.


Copyright 2013 Ceptah Solutions
http://www.ceptah.com