If you want to preconfigure settings for users can create a settings file and deploy it:
Locate the "Credentials" section of each configured server and replace it by:
"Credentials": {
"Username": "",
"Password": "",
"ApiToken": ""
}, |
When the user creates a ticket for the first time, the configuration settings will open. After that he needs to edit the connection settings and enter the username, password and API token (Jira Cloud only).
Make sure to keep the JSON valid, otherwise the Add-In will not be able to process it. Please pay special attention to the commas at the end. You can also use an online JSON validator to make sure, the syntax is valid. Furthermore, you should test the settings file before you deploy it. Last but not least: Not all key-value pairs in the configuration file are logically correct. Do not care about any true or false for values, just trust the configuration made in Outlook. |
If you want to share settings in your team, for example project mappings, which map e-mail addresses to Jira projects, you can just copy the related sections from one settings file to another. In case you configured multiple servers you can also copy settings from one server to another.
Locate the server and settings you want to share or copy, for example project mappings:
"RegExProjectMapping": [
{
"ProjectKey": "COMPANY",
"RegexPattern": "*@company.com"
},
{
"ProjectKey": "SUPPORT",
"RegexPattern": "support@???.server.com"
},
{
"ProjectKey": "USERS",
"RegexPattern": "???.*@company.net"
}
] |
Make sure to keep the JSON valid. Please pay special attention to the commas at the end. You can also use an online JSON validator to make sure, the syntax is valid. Last but not least: Not all key-value pairs in the configuration file are logically correct. Do not care about any true or false for values, just trust the configuration made in Outlook. |