Search
Results (2548)
- Revision 566 (svn): Added per user custom queries.
- Any logged in user can now save queries (they ... ports" view. It can now be accessed from the issues list.
- Revision 562 (svn): Fixed version field on issue view page now links to the corresponding version in the roadmap.
- Revision 560 (svn): Added an error message when trying to create an issue with no default status defined.
- Revision 558 (svn): Added :dependent => :delete_all on IssueStatus Workflow association.
- Also added compact in find_new_statuses_allowed_to to remove nil statuses.
- Revision 551 (svn): Fixed: open/closed issue counts are always 0 on reports view (postgresql)
- Revision 549 (svn): Added the ability to archive projects:
- * Only administrators can archive/unarchive p ... narchive preserve everything on the project (issues, members, ...). * A subproject can not be unarchived if its parent project is archived.
- Revision 543 (svn): Added issue count details for versions on Reports view.
- Revision 541 (svn): Attachments can now be ad ... authorized users can add/delete attachments.
- Attached images can be displayed inline, using textile image tag (for wiki pages, issue descriptions and forum messages).
- Revision 535 (svn): Fixed: performance issue on RepositoriesController#revisions when a changeset has a great number of changes (eg. 100,000).
- Also added pagination for changes on changeset details view.
- Revision 523 (svn): Added a simple mail handler.
- It lets users add notes to an existing issue by replying to the initial notification emai ... r RedMine mail hander is MailHandler#receive
- Revision 513 (svn): Added a "clear" link when ... uery. It clears the query filter to show all issues.
- Revision 511 (svn): Ajaxified issue filter reset link
- Revision 510 (svn): Issue#long_id no more used and removed
- Revision 507 (svn): Issue filter no more reseted when clicking 'Issues' menu link
- 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.