##// END OF EJS Templates
u » ewong » rhodecode-enterprise-ce-fork
RSS

Fork of rhodecode-enterprise-ce

auth: don't break hashing in case of user with empty password....
auth: don't break hashing in case of user with empty password. In some cases such as LDAP user created via external scripts users might set the passwords to empty. The hashing uses the md5(password_hash) to store reference to detect password changes and forbid using the same password. In case of pure LDAP users this is not valid, and we shouldn't raise Errors in such case. This change makes it work for empty passwords now.
lisaq - - Load All Authors

File last commit:

r645:c8c27324 default
r2203:8a18c3c3 default
Show More
jira.rst
27 lines | 813 B | text/x-rst | RstLexer
/ docs / integrations / jira.rst
History | Annotation | Raw |Copy content |Copy permalink

JIRA integration

Important

JIRA integration is only available in |RCEE|.

Important

In order to make issue numbers clickable in commit messages, see the :ref:`rhodecode-issue-trackers-ref` section. The JIRA integration only deals with altering JIRA issues.

The JIRA integration allows you to reference and change issue statuses in JIRA directly from commit messages using commit message patterns such as fixes #JIRA-235 in order to change the status of issue JIRA-235 to eg. "Resolved".

In order to apply a status to a JIRA issue, it is necessary to find the transition status id in the Workflow section of JIRA.

Once you have the transition status id, you can create a JIRA integration as outlined in :ref:`creating-integrations`.