This will cover your examples as far as I can see. This enhancement is included in Redmine 0.9.0 and makes it possible to actually prevent issues from being set into statuses which are configured as being considered as closed when a 'blocked by' relation is active for an issue which doesn't have a status which isn't closed (yet). B and C are parts of A, so A can't be closed unless B and C are, or B blocking A makes A uncloseable …), and in that is somewhat related to #443.įelix, please note r2800 which resolved issue #1740. relationships that enforce possible or not possible states and attributes in the other tickets (i.e. This request has a broader scope though, and calls for harder "dependencies", i.e. relationships that only link issues to one another and don't enforce anything (the exception being follows/precedes), are implemented, and afaik that's what bugzilla has to offer to. Hugo, you are right that what I'd call "lazy relationships", i.e. So if an issue is moved to anotherĬircular dependencies are checked when creating a relation. To set a relation, the 2 issues have to belong to the same project When setting datesįor an issue, dates of all downstream issues are set according Issue depends on the due date of the preceding issue (implemented).Ī delay can be set so that the related issue can only start nĭays after the end of the preceding issue. precedes (end to start relation): start date of the related.blocks: will require to close the blocking issue before closing.When closing the issue (not implemented yet) duplicates: will close the related issue with the same status.Issue relations first commit (not thoroughly tested). Set the permissions for adding and removing relations.
#WEBDOT GRAPHVIZ UPDATE#
If you want to have a try, just update your installation and