4 Commits (99914bb95c18aa50ae1e83408024fad0b873079e)

Author	SHA1	Message	Date
Gregor Schmidt	6408cddc40	[#374] Not escaping URLs since they are used in a safe CDATA section, where no entity encoding is needed.	14 years ago
Jean-Philippe Lang	a8b12bcb52	Autocomplete issue relations on subject (#3170). ... git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@4502 e93f8b46-1217-0410-a6f0-8f06a7374b81	14 years ago
Jean-Philippe Lang	827e998afe	Application layout refactored. ... The project menu is now the main menu. git-svn-id: http://redmine.rubyforge.org/svn/trunk@747 e93f8b46-1217-0410-a6f0-8f06a7374b81	17 years ago
Jean-Philippe Lang	92b02014d2	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 issue is moved to another project, all its relations are removed. Circular dependencies are checked when creating a relation. git-svn-id: http://redmine.rubyforge.org/svn/trunk@506 e93f8b46-1217-0410-a6f0-8f06a7374b81	18 years ago