2. Submission and provider configuration

Submission and provider settings

Submission is a process of creating a Jira ticket in assigned project. With that deployment team is getting notified about new plan that should be reviewed and applied/revoked.

Submission have following settings:

1. Project: any Jira project where You want to create tickets related to plans. When plan will be submitted by user, new issues will appear in the project.

2. Issue type: Issue type, available inside selected project. Submissions will have selected issue types.

3. Label: Optionally, you can assign label to tickets created as a plan submission.

4. Additional config: Some projects requires additional configuration of fields. If during the tests, you will see error messages about additional fields not being set, it's a signal that you should assign some values in JSON form in the box below.

5. Plan id custom field should be a simple text file, that will store information about plan ID. Value is set when submitting a plan. Remember that field should be added to proper screens in selected project.

6. This button creates new custom field with proper type and name "PlanApply Plan ID". You can later select this field in option mentioned in 5. Remember that field should be added to proper screens in selected project.

7. Settings tools:

   1. Use "Save / Update" to save settings from left side of configuration.

   2. Use "Test" to verify if issue can be created properly.

   3. Use "Delete" to remove saved settings entirely.

8. You will see error / success messages displayed here from Test operation. It is useful in case of debug. If there is a field mentioned as required but not set, apply it to "Additional / Required configuration (JSON format)"

9. Provider settings. They are used to unlock "Import resources" option in global page - Designer. Username: username / email Token: Personal Access Token created for given account. ☝️Desginer will use provided credentials to import resources. Permissions and data visible as an outcome of this action is inherited from provided account.

10. Use "Save / Update" to store credentials and "Delete" to remove them. Removing will disable Designer feature again.

Provider configuration is stored in Atlassian Forge secret storage. If you want to rotate password, simply replace and save it.

You don't have to store credentials in plain text inside Terraform scripts. You can select option "Use public provider" in Terraform console to append a volatile file with stored credentials during Terraform operations.

This temporary file will not be stored or returned as the result of the operation and used only to append Terraform provider configuration.