Skip to content

Commit 2cbc9ca

Browse files
Updated documentation
1 parent 05882f3 commit 2cbc9ca

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/CONFIGURATION.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -27,9 +27,9 @@ This section is optional if you don't intend to use the Jira ticket generator.
2727

2828
In order to configure the extended configuration for Jira, you need to retrieve configuration values __which are specific to your JIRA installation__. Please see [this article](https://community.atlassian.com/t5/Jira-Software-questions/Project-ID-and-Custom-Field-ID-on-next-gen-project/qaq-p/1095295) for additional details. In addition, this program assumes that you [have the Jira XRay plugin installed](https://www.getxray.app/). You can still use the program without XRay support but might be required to apply small changes to both code and template files
2929

30-
Prerequisites for this configurationstep:
30+
Prerequisites for this configuration step:
3131

32-
- Get your numeric Jira project ID
32+
- Determine your numeric Jira project ID
3333
- Get the ``customfield_...`` value for your Jira/XRay installation's ``Test Environments`` field. Dependent on your setup, you can use this field for e.g. passing environment variables from Jira/XRay to other connected system component.
3434
- In order to allow the program to create these tickets, you need to provide a Jira Access key to the program. Contact your administrator if necessary. The access key may look like this: ``dGVu9Y3lfcm9ib3Q6M08lKADt9vTVhnchhaUnQ9``
3535

@@ -69,4 +69,4 @@ There are two XRay dependencies which need to be amended:
6969
- Amend the ``create_jira_tickets`` function in the code and disable the XRay API calls.
7070

7171

72-
Have a look at the program's [command line parameters and known issues](USAGE.md)
72+
Have a look at the program's [command line parameters and known issues](USAGE.md)

0 commit comments

Comments
 (0)