Content
View differences
Updated by Robin Wagner over 12 years ago
**Preconditions**
- Repository module is activated.
- Work package module is activated and work package exists (with different status than the “Applied status” (see below)).
- “Fixing keyword” and “Applied status” have been specified in Repository settings (Modules \> Administration \> Settings \> Repository)
- SVN-client is being used (e.g. Tortoise SVN) and repository is checked out locally.
**Steps to reproduce**
1. Make a change to a document in the local repository (or add a new document).
2. Commit the document to the web repository and use the specified keyword to change the status (e.g. “fixes \#123”).
3. (Document is committed but work package is not changed to “Applied status”)
**Actual behavior**
- Work package status cannot be changed via keyword.
**Expected behavior**
- Work package status is changed to specified status.
**QA system**
- preview.openproject.org: Version 5.0.pre34
- Core version: 3.0.0pre48
- Repository module is activated.
- Work package module is activated and work package exists (with different status than the “Applied status” (see below)).
- “Fixing keyword” and “Applied status” have been specified in Repository settings (Modules \> Administration \> Settings \> Repository)
- SVN-client is being used (e.g. Tortoise SVN) and repository is checked out locally.
**Steps to reproduce**
1. Make a change to a document in the local repository (or add a new document).
2. Commit the document to the web repository and use the specified keyword to change the status (e.g. “fixes \#123”).
3. (Document is committed but work package is not changed to “Applied status”)
**Actual behavior**
- Work package status cannot be changed via keyword.
**Expected behavior**
- Work package status is changed to specified status.
**QA system**
- preview.openproject.org: Version 5.0.pre34
- Core version: 3.0.0pre48