Jira - PSA Priority and Status Value Mappings Foundations Configuration Item Fields

Here is a description of the Foundations configuration item fields used by the Integration Hub Connector: Jira - PSA to define priority and status value mappings. For more information, see Customizing the Priority and Status Value Mappings.

Note:

Foundations configuration items are used in various processes across the FinancialForce product suite. For a full list of fields and descriptions, see Foundations Configuration Item Custom Metadata Type Fields.

IHC Jira-PSA Priority & Status Mappings Foundations Configuration Item Fields
Field	Description
Label	Label of the Foundations configuration item metadata type record. The predefined record is labeled IHC Jira-PSA Priority & Status Mappings. You can use the same label when creating a new record.
Foundations Configuration Item Name	Unique name of the Foundations configuration item metadata type record. When creating a new record, you can append the version to make the value unique, for example, IHC_Jira_PSA_Priority_Status_Mappings2.
Process	Name of the process that this Foundations configuration item relates to. Warning: This must be set to psa:ihc:jira. Otherwise, the record is not used by the connector.
Small Data	Version of the mappings record. When creating a new record, you must enter a whole number and increment the value from the previous record by one. For example, enter 2 to overwrite the predefined mappings records.
Large Data	JSON structure that defines the value mappings. See Large Data JSON Attributes and Large Data JSON Examples.
Object	Not used by the connector. Leave "None".
Field	Not used by the connector. Leave "None".
Identifier	Identifier of this record. Warning: This must be set to project-task:mappings. Otherwise, the record is not used by the connector.
Enabled	Indicates that the record is enabled. This must be selected.

Large Data JSON Attributes

Here a description of all the attributes available in the Large Data JSON structure.

Notes:

The Large Data value of the predefined record contains the mappings for both the Sync Project Tasks from PSA to Issues in Jira and Sync Issues from Jira to Project Tasks in PSA workflows. Depending on the workflow you plan on enabling, you must modify the appropriate attributes as listed in the table below.
We recommend editing the JSON structure in a text editor with syntax highlighting or an online editor that displays the JSON in tree-view format. This helps minimize user errors.
We also recommend checking the final value in an online JSON validator to make sure that you have not made any syntax errors.
Due to Salesforce limitations, validations cannot be applied to a custom metadata record. If the JSON structure does contain errors, you are notified when you try to activate the relevant workflow using the Feature Console.

Warnings:

All the root level attributes are required for the Sync Project Tasks from PSA to Issues in Jira workflow.
The following root level attributes are required for the Sync Issues from Jira to Project Tasks in PSA workflow:
- JiraToPSAStatusMappings
- JiraToPSAPriorityMappings
When a root level attribute is present, all of its child attributes are required.
The examples for project-specific mappings included in the predefined (managed) record are provided to help you create your own mappings. If you only want to define default mappings, do not remove the examples because it will cause an error.

Large Data JSON Attributes
Root Level Attribute	Level 1 Attribute	Level 2 Attribute	Level 3 Attribute	Description
`PSAToJiraStatusMappings`				Defines how PSA project task status values are mapped to Jira issue statuses. This is used by the Sync Project Tasks from PSA to Issues in Jira workflow. Note: If you are planning on syncing issues from Jira to project tasks in PSA, you can remove this object and its child attributes. Even if you don't remove it, it is ignored.
	`DefaultStatusValuesMapping`			Defines the default status value mapping applied for all projects except for the ones explicitly defined in `ProjectSpecificMappings`. You must enter a key-value pair for each PSA status, where the key is the PSA status and the value is the corresponding Jira status. For example, Copy `"DefaultStatusValuesMapping": { "Draft": "To Do", "Planned": "To Do", "Started": "In Progress", "Blocked": "In Progress", "Complete": "Done", "Deferred": "Done" },`
	`ProjectSpecificMappings`			Defines the project-specific status mappings that override the default mapping. You can create as many project-specific mappings as you require.
		(mapping name)		Unique name of the project-specific mapping. We recommend giving the object a descriptive name, for example, `ImplementationProjects`.
			`JiraProjectKeys`	Defines the Jira projects the mapping applies to, identified by their Jira key. For example, Copy `"JiraProjectKeys": [ "PSA", "FDN" ],`
			`StatusValuesMapping`	Defines the status value mapping for the specified projects. You must enter a key-value pair for each PSA status, where the key is the PSA status and the value is the corresponding Jira status. For example, Copy `"StatusValuesMapping": { "Draft": "Backlog", "Planned": "To Do", "Started": "In Progress", "Blocked": "Pull Blocked", "Complete": "Done", "Deferred": "Won't Do" }`
`PSAToJiraPriorityMappings`				Defines how PSA project task priority values are mapped to Jira issue priorities. This is used by the Sync Project Tasks from PSA to Issues in Jira workflow. Note: If you are planning on syncing issues from Jira to project tasks in PSA, you can remove this object and its child attributes. Even if you don't remove it, it is ignored.
	`DefaultPriorityValuesMapping`			Defines the default priority value mapping applied for all projects except for the ones explicitly defined in `ProjectSpecificMappings`. You must enter a key-value pair for each PSA priority, where the key is the PSA priority and the value is the corresponding Jira priority. For example, Copy `"DefaultPriorityValuesMapping": { "P5": "Highest", "P4": "High", "P3": "Medium", "P2": "Low", "P1": "Lowest" },`
	`ProjectSpecificMappings`			Defines the project-specific priority mappings that override the default mapping. You can create as many project-specific mappings as you require.
		(mapping name)		Unique name of the project-specific mapping. We recommend giving the object a descriptive name, for example, `LiveCustomers`.
			`JiraProjectKeys`	Defines the Jira projects the mapping applies to, identified by their Jira key. For example, Copy `"JiraProjectKeys": [ "SL1", "SL2", "SL3" ],`
			`PriorityValuesMapping`	Defines the priority value mapping for the specified projects. You must enter a key-value pair for each PSA priority, where the key is the PSA priority and the value is the corresponding Jira priority. For example, Copy `"PriorityValuesMapping": { "P5": "Business Standstill", "P4": "Showstopper", "P3": "Severe Performance Impact", "P2": "Major Issue", "P1": "Minor Issue" }`
`JiraToPSAStatusMappings`				Defines how Jira issue status values are mapped PSA project task statuses. This is used by both the Sync Project Tasks from PSA to Issues in Jira and Sync Issues from Jira to Project Tasks in PSA workflows. Warning: For the Sync Project Tasks from PSA to Issues in Jira workflow, you must ensure that status mappings defined here and in the `PSAToJiraStatusMappings` attribute logically match. This means that each Jira status that was mapped as the target for a PSA status, must map back to that status when it becomes the source. For example, if you map the "Draft" and "Planned" PSA statuses to "To Do" in Jira, then you must map the "To Do" Jira status to either "Draft" or "Planned" in PSA. Otherwise, you might encounter unexpected results in PSA.
	`DefaultStatusValuesMapping`			Defines the default status value mapping applied for all projects except for the ones explicitly defined in `ProjectSpecificMappings`. You must enter a key-value pair for each Jira status, where the key is the Jira status and the value is the corresponding PSA status. For example, Copy `"DefaultStatusValuesMapping": { "Open": "Draft", "In Progress": "Started", "Done": "Complete", "To Do": "Planned", "Under Review": "Planned", "Cancelled": "Deferred" },`
	`ProjectSpecificMappings`			Defines the project-specific status mappings that override the default mapping. You can create as many project-specific mappings as you require.
		(mapping name)		Unique name of the project-specific mapping. We recommend giving the object a descriptive name, for example, `ImplementationProjects`.
			`JiraProjectKeys`	Defines the Jira projects the mapping applies to, identified by their Jira key. For example, Copy `"JiraProjectKeys": [ "PSA", "FDN" ],`
			`StatusValuesMapping`	Defines the status value mapping for the specified projects. You must enter a key-value pair for each Jira status, where the key is the Jira status and the value is the corresponding PSA status. For example, Copy `"StatusValuesMapping": { "Backlog": "Draft", "To Do": "Planned", "In Progress": "Started", "Pull Blocked": "Blocked", "Done": "Complete", "Won't Do": "Deferred" }`
`JiraToPSAPriorityMappings`				Defines how Jira issue priority values are mapped PSA project task priorities. This is used by the Sync Issues from Jira to Project Tasks in PSA workflow. Warnings: Do not remove this object even if you are planning on syncing project tasks from PSA to issues in Jira. It is required to, although the values are not used in this case.
	`DefaultPriorityValuesMapping`			Defines the default priority value mapping applied for all projects except for the ones specifically defined in `ProjectSpecificMappings`. You must enter a key-value pair for each Jira priority, where the key is the Jira priority and the value is the corresponding PSA priority. For example, Copy `"DefaultPriorityValuesMapping": { "Highest": "P5", "High": "P4", "Medium": "P3", "Low": "P2", "Lowest": "P1" },`
	`ProjectSpecificMappings`			Defines the project-specific priority mappings that override the default mapping. You can create as many project-specific mappings as you require.
		(mapping name)		Unique name of the project-specific mapping. We recommend giving the object a descriptive name, for example, `LiveCustomers`.
			`JiraProjectKeys`	Defines the Jira projects the mapping applies to, identified by their Jira key. For example, Copy `"JiraProjectKeys": [ "SL1", "SL2", "SL3" ],`
			`PriorityValuesMapping`	Defines the priority value mapping for the specified projects. You must enter a key-value pair for each PSA priority, where the key is the PSA priority and the value is the corresponding Jira priority. For example, Copy `"PriorityValuesMapping": { "Business Standstill": "P5", "Showstopper": "P5", "Severe Performance Impact": "P5", "Major Issue": "P4", "Minor Issue": "P4" }`

Large Data JSON Examples

Sync Project Tasks from PSA to Issues in Jira Example

Copy

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
[
    {
        "PSAToJiraStatusMappings": {
            "DefaultStatusValuesMapping": {
                "Draft": "To Do",
                "Planned": "To Do",
                "Started": "In Progress",
                "Blocked": "In Progress",
                "Complete": "Done",
                "Deferred": "Done"
            },
            "ProjectSpecificMappings": [
                {
                    "ImplementationProjects": {
                        "JiraProjectKeys": [
                            "PSA",
                            "IHC"
                        ],
                        "StatusValuesMapping": {
                            "Draft": "Backlog",
                            "Planned": "To Do",
                            "Started": "In Progress",
                            "Blocked": "Pull Blocked",
                            "Complete": "Done",
                            "Deferred": "Won't Do"
                        }
                    }
                }
            ]
        }
    },
    {
        "PSAToJiraPriorityMappings": {
            "DefaultPriorityValuesMapping": {
                "P5": "Highest",
                "P4": "High",
                "P3": "Medium",
                "P2": "Low",
                "P1": "Lowest"
            },
            "ProjectSpecificMappings": [
                {
                    "LiveCustomers": {
                        "JiraProjectKeys": [
                            "SL1",
                            "SL2",
                            "SL3"
                        ],
                        "PriorityValuesMapping": {
                            "P5": "Business Standstill",
                            "P4": "Showstopper",
                            "P3": "Severe Performance Impact",
                            "P2": "Major Issue",
                            "P1": "Minor Issue"
                        }
                    }
                }
            ]
        }
    },
    {
        "JiraToPSAStatusMappings": {
            "DefaultStatusValuesMapping": {
                "Open": "Draft",
                "In Progress": "Started",
                "Done": "Complete",
                "To Do": "Planned",
                "Under Review": "Planned",
                "Cancelled": "Deferred"
            },
            "ProjectSpecificMappings": [
                {
                    "ImplementationProjects": {
                        "JiraProjectKeys": [
                            "PSA",
                            "IHC"
                        ],
                        "StatusValuesMapping": {
                            "Backlog": "Draft",
                            "To Do": "Planned",
                            "In Progress": "Started",
                            "Pull Blocked": "Blocked",
                            "Done": "Complete",
                            "Won't Do": "Deferred"
                        }
                    }
                }
            ]
        }
    },
    {
        "JiraToPSAPriorityMappings": {
            "DefaultPriorityValuesMapping": {
                "Highest": "P5",
                "High": "P4",
                "Medium": "P3",
                "Low": "P2",
                "Lowest": "P1"
            },
            "ProjectSpecificMappings": [
                {
                    "LiveCustomers": {
                        "JiraProjectKeys": [
                            "SL1",
                            "SL2",
                            "SL3"
                        ],
                        "PriorityValuesMapping": {
                            "Business Standstill": "P5",
                            "Showstopper": "P5",
                            "Severe Performance Impact": "P5",
                            "Major Issue": "P4",
                            "Minor Issue": "P4"
                        }
                    }
                }
            ]
        }
    }
]

Sync Issues from Jira to Project Tasks in PSA Example