redmine.git - Mirror of redmine code source: https://github.com/redmine/redmine

	Commit message (Collapse)	Author	Age	Files	Lines
...
*	Fixed circular dependencies possibly introduced when using reverse ↵	Jean-Baptiste Barth	2011-06-26	1	-1/+6
\| \| \| \| \| \|	relations, for instance "blocked by" relations (#8616). git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@6124 e93f8b46-1217-0410-a6f0-8f06a7374b81
*	Safer code in IssueRelation (#7018).	Jean-Philippe Lang	2010-12-04	1	-3/+4
\| \| \| \|	git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@4467 e93f8b46-1217-0410-a6f0-8f06a7374b81
*	Adds issue relations to individual issue XML (#5305).	Jean-Philippe Lang	2010-05-01	1	-7/+18
\| \| \| \|	git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@3729 e93f8b46-1217-0410-a6f0-8f06a7374b81
*	Makes subtasks rescheduled when a 'precedes' relation is set on a parent task.	Jean-Philippe Lang	2010-03-13	1	-3/+2
\| \| \| \|	git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@3574 e93f8b46-1217-0410-a6f0-8f06a7374b81
*	Adds subtasking (#443) including:	Jean-Philippe Lang	2010-03-13	1	-0/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* priority, start/due dates, progress, estimate, spent time roll-up to parent issues * descendant issues tree displayed on the issue view with context menu support * issue tree display on the gantt chart * issue tree copy on project copy * unlimited nesting Defining subtasks requires the new permission 'Manage subtasks'. Subtasks can not belong to a different project than the parent task. Implementation is based on scoped nested sets for fast reads and updates. git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@3573 e93f8b46-1217-0410-a6f0-8f06a7374b81
*	Adds 'Blocked by' (#1755) and 'Duplicated by' relation types to the dropdown ↵	Jean-Philippe Lang	2010-02-28	1	-5/+10
\| \| \| \| \| \|	menu for new relations. git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@3512 e93f8b46-1217-0410-a6f0-8f06a7374b81
*	Fixes 'follows' relation validation.	Jean-Philippe Lang	2009-12-18	1	-3/+3
\| \| \| \|	git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@3191 e93f8b46-1217-0410-a6f0-8f06a7374b81
*	Adds 'follows' relation (#1432).	Jean-Philippe Lang	2009-12-18	1	-1/+16
\| \| \| \|	git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@3190 e93f8b46-1217-0410-a6f0-8f06a7374b81
*	Merged Rails 2.2 branch. Redmine now requires Rails 2.2.2.	Jean-Philippe Lang	2009-02-21	1	-3/+3
\| \| \| \|	git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@2493 e93f8b46-1217-0410-a6f0-8f06a7374b81
*	Fixed: users should not be able to add relations with issues they're not ↵	Jean-Philippe Lang	2009-01-27	1	-0/+2
\| \| \| \| \| \|	allowed to view (#2589). git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@2323 e93f8b46-1217-0410-a6f0-8f06a7374b81
*	Make the 'duplicates of' relation asymmetric:	Jean-Philippe Lang	2008-06-03	1	-1/+1
\| \| \| \| \| \| \|	* closing a issue will close its duplicates * closing a duplicate won't close the main issue git-svn-id: http://redmine.rubyforge.org/svn/trunk@1488 e93f8b46-1217-0410-a6f0-8f06a7374b81
*	Added an option to be able to relate issues in different projects.	Jean-Philippe Lang	2007-08-12	1	-1/+1
\| \| \| \| \| \|	It can be set in Admin -> Settings (default: false). git-svn-id: http://redmine.rubyforge.org/svn/trunk@620 e93f8b46-1217-0410-a6f0-8f06a7374b81
*	Issue relations first commit (not thoroughly tested). 4 kinds of relation ↵	Jean-Philippe Lang	2007-05-05	1	-0/+79
	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