Search
Results (2584)
- Revision 506 (svn): Issue relations first commit (not thoroughly tested). 4 kinds of relation are available:
- * relates to: do nothing special. Just to know that the 2 issues are related... * duplicates: will close the related issue with the same status when closing the issue (not implemented yet) * blocks: will require to close the blocking issue before closing the blocked issue (not implemented yet) * precedes (end to start relation): start date of the related issue depends on the due date of the preceding issue (implemented). A delay can be set so that the related issue can only start n days after the end of the preceding issue. When setting dates for an issue, dates of all downstream issues are set according to these relations. To set a relation, the 2 issues have to belong to the same project (may change in the future). So if an ...
- Revision 498 (svn): Issue subjects column width set to 330 on gantt chart
- Revision 489 (svn): Added a quick search form ... unctionality moved to a dedicated controller.
- When used: * outside of a project: searches projects * inside a project: searches issues, changesets, news, documents and wiki pages of the current project If an issue number is given, user is redirected to the corresponding issue.
- Revision 484 (svn): Subproject name displayed on issue list, calendar and gantt (only for issues that belong to a subproject).
- Revision 479 (svn): Fixed: 10342 Creation of Schema in Oracle
- Comment is a reserved keyword for Oracle. The ... old' name). Fixed also a few oracle specific issues. Note: currently (in Rails 1.2.3), there's ... tch is required for redMine to work properly.
- Revision 477 (svn): Fixed 10335 Error in journalizing an issue with longtext custom fields (Postgresql)
- Revision 475 (svn): Fixed: default status not showing in new issue
- Revision 474 (svn): Fixed 10337 Regression: Admin raises issue in project not assigned to
- Revision 473 (svn): Commit messages are now scanned for referenced or fixed issue IDs.
- Keywords and the status to apply to fixed issues can be defined in Admin -> Settings. Default keywords: - for referencing issues: refs, references, IssueID - for fixing issues: fixes,closes There's no default status defined for fixed issue. You'll have to specify it if you want to enable auto closure of issues. Example of a working commit message: "This commit references #1, #2 and fixes #3"
- Revision 470 (svn): The ability to change the issue status to the same status is no longer forced.
- This behaviour can be defined in workflow setup.
- Revision 467 (svn): Grey scale icon for issue not watched.
- Revision 466 (svn): Fixed: error on history atom feed when there's no notes on an issue change
- Revision 465 (svn): Fixed 10058: issue URL in repository comment break
- Revision 456 (svn): Added a new block available for my page: "Watched issues"
- Revision 453 (svn): Added "Watch" functionality on issues. It allows users to receive mail notifications about issue changes.
- For now, it's only usefull for users who are ... since members receive notifications for each issue (this behaviour will change).
- Revision 452 (svn): Fixed: error when exporting to PDF an issue list using a custom field filter.
- Revision 447 (svn): Custom fields for issues can now be used as filters on issue list.
- To use a custom field as a filter, check "Used as a filter" on the custom field edit screen.
- Revision 442 (svn): Closed issues no longer displayed on "my page" -> "issues assigned to me".
- Revision 431 (svn): Added link_to_issue helper.
- Revision 425 (svn): Feature 9867 Allow file upload in comment and add to issue history
- Revision 422 (svn): "Author" column replaced by "Assigned to" in issue list.
- "Assigned to" column added in the csv export.
- Revision 420 (svn): Fixed a regression (crash ... with no role on the project try to create an issue)
- Revision 414 (svn): Various code cleaning, mainly on User, Permission and IssueStatus models.
- Revision 412 (svn): Feature #9808 Allow user to "change" issue status to the same status
- Revision 410 (svn): Added subprojects issue count on project "Reports" page