Show More
@@ -1,27 +1,34 b'' | |||||
1 | .. _integrations-jira: |
|
1 | .. _integrations-jira: | |
2 |
|
2 | |||
3 | JIRA integration |
|
3 | JIRA integration | |
4 | ================ |
|
4 | ================ | |
5 |
|
5 | |||
6 | .. important:: |
|
6 | .. important:: | |
7 |
|
7 | |||
8 | JIRA integration is only available in |RCEE|. |
|
8 | JIRA integration is only available in |RCEE|. | |
9 |
|
9 | |||
10 |
|
10 | |||
11 | .. important:: |
|
11 | .. important:: | |
12 |
|
12 | |||
13 | In order to make issue numbers clickable in commit messages, see the |
|
13 | In order to make issue numbers clickable in commit messages, see the | |
14 | :ref:`rhodecode-issue-trackers-ref` section. The JIRA integration |
|
14 | :ref:`rhodecode-issue-trackers-ref` section. The JIRA integration | |
15 | only deals with altering JIRA issues. |
|
15 | only deals with altering JIRA issues. | |
16 |
|
16 | |||
17 |
|
17 | |||
18 | The JIRA integration allows you to reference and change issue statuses in |
|
18 | The JIRA integration allows you to reference and change issue statuses in | |
19 | JIRA directly from commit messages using commit message patterns such as |
|
19 | JIRA directly from commit messages using commit message patterns such as | |
20 | ``fixes #JIRA-235`` in order to change the status of issue JIRA-235 to |
|
20 | ``fixes #JIRA-235`` in order to change the status of issue JIRA-235 to | |
21 | eg. "Resolved". |
|
21 | eg. "Resolved". | |
22 |
|
22 | |||
23 | In order to apply a status to a JIRA issue, it is necessary to find the |
|
23 | In order to apply a status to a JIRA issue, it is necessary to find the | |
24 | transition status id in the *Workflow* section of JIRA. |
|
24 | transition status id in the *Workflow* section of JIRA. | |
25 |
|
25 | |||
26 | Once you have the transition status id, you can create a JIRA integration |
|
26 | Once you have the transition status id, you can create a JIRA integration | |
27 | as outlined in :ref:`creating-integrations`. |
|
27 | as outlined in :ref:`creating-integrations`. | |
|
28 | ||||
|
29 | ||||
|
30 | .. note:: | |||
|
31 | ||||
|
32 | There's an option to configure integration templates. | |||
|
33 | Please see :ref:`integrations-rcextensions` section. | |||
|
34 | rcextensions examples are here: https://code.rhodecode.com/rhodecode-enterprise-ce/files/default/rhodecode/config/rcextensions/examples/custom_integration_templates.py |
@@ -1,28 +1,34 b'' | |||||
1 | .. _integrations-redmine: |
|
1 | .. _integrations-redmine: | |
2 |
|
2 | |||
3 | Redmine integration |
|
3 | Redmine integration | |
4 | =================== |
|
4 | =================== | |
5 |
|
5 | |||
6 | .. important:: |
|
6 | .. important:: | |
7 |
|
7 | |||
8 | Redmine integration is only available in |RCEE|. |
|
8 | Redmine integration is only available in |RCEE|. | |
9 |
|
9 | |||
10 |
|
10 | |||
11 | .. important:: |
|
11 | .. important:: | |
12 |
|
12 | |||
13 | In order to make issue numbers clickable in commit messages, see the section |
|
13 | In order to make issue numbers clickable in commit messages, see the section | |
14 | :ref:`rhodecode-issue-trackers-ref`. Redmine integration is specifically for |
|
14 | :ref:`rhodecode-issue-trackers-ref`. Redmine integration is specifically for | |
15 | altering Redmine issues. |
|
15 | altering Redmine issues. | |
16 |
|
16 | |||
17 |
|
17 | |||
18 | Redmine integration allows you to reference and change issue statuses in |
|
18 | Redmine integration allows you to reference and change issue statuses in | |
19 | Redmine directly from commit messages, using commit message patterns such as |
|
19 | Redmine directly from commit messages, using commit message patterns such as | |
20 | ``fixes #235`` in order to change the status of issue 235 to eg. "Resolved". |
|
20 | ``fixes #235`` in order to change the status of issue 235 to eg. "Resolved". | |
21 |
|
21 | |||
22 | To set a Redmine integration up, it is first necessary to obtain a Redmine API |
|
22 | To set a Redmine integration up, it is first necessary to obtain a Redmine API | |
23 | key. This can be found under *My Account* in the Redmine application. |
|
23 | key. This can be found under *My Account* in the Redmine application. | |
24 | You may have to enable API Access in Redmine settings if it is not already |
|
24 | You may have to enable API Access in Redmine settings if it is not already | |
25 | available. |
|
25 | available. | |
26 |
|
26 | |||
27 | Once you have the API key, create a Redmine integration as outlined in |
|
27 | Once you have the API key, create a Redmine integration as outlined in | |
28 | :ref:`creating-integrations`. |
|
28 | :ref:`creating-integrations`. | |
|
29 | ||||
|
30 | ||||
|
31 | .. note:: | |||
|
32 | ||||
|
33 | There's an option to configure integration templates. Please see :ref:`integrations-rcextensions` section. | |||
|
34 | rcextensions examples are here: https://code.rhodecode.com/rhodecode-enterprise-ce/files/default/rhodecode/config/rcextensions/examples/custom_integration_templates.py No newline at end of file |
General Comments 0
You need to be logged in to leave comments.
Login now