A Task Mapping strategy - is a set of rules, which define, how the issues from Jira are mapped to tasks from FreshBooks.
Different Task Mapping strategies give the ability to map issues to tasks differently:
1. "Each Issue is a Task"— a strategy, which makes the plugin to create a separate task for each issue (found in each of the projects [or issue filters], given in the ProjectMapping). The name of the created task is able to choose from a section "Choose FreshBooks Task name". The description of the issue becomes the description of the created task. Whenever the issue is updated - the task is updated with it, accordingly. Thus:
...
Lets prepose, that we have the following project mapping:
| Jira project or filter | FreshBooks project |
|---|---|
| JiraProject | FbProject |
Also, assume that we have the following user mapping:
| Jira user | FreshBooks staff |
|---|---|
| JiraUser | FbStaff |
Suppose, that we have created an issue in the JiraProject - JiraIssue.
The plugin finds the corresponding FreshBooks project - FbProject, and creates a task inside it - the FbTask.
...
Lets prepose, that we have the following task mapping:
| Jira issue filter | FreshBooks task | FreshBooks project |
|---|---|---|
| All issues from JiraProject | FbTask | FbProject |
Also, assume that we have the following user mapping:
| Jira user | FreshBooks staff |
|---|---|
| JiraUser | FbStaff |
Suppose, that we have created an issue, which fits the filter "All issues from JiraProject" (i.e. we created an issue in the JiraProject ) - JiraIssue.
The plugin finds the corresponding FreshBooks task - FbTask,
and updates it for Freshbooks project from the task map - FbProject.
...