Jira has a reminder plugin that will annoy (remind) the assignee if he has not updated the ticket.
I don't know if apache has it enabled, if not, may be we can look into making a crawler that goes out and look for tickets that have not been updated for "x" number of days - and if found, send a reminder. -----Original Message----- From: David Nalley [mailto:da...@gnsa.us] Sent: Tuesday, February 05, 2013 6:42 PM To: Marcus Sorensen Cc: Chip Childers; Animesh Chaturvedi; cloudstack-dev@incubator.apache.org Subject: Re: [ACS41] Can folks please take responsibility for updating their own Jira tickets? On Tue, Feb 5, 2013 at 6:22 PM, Marcus Sorensen <shadow...@gmail.com> wrote: > On Tue, Feb 5, 2013 at 4:15 PM, David Nalley <da...@gnsa.us> wrote: >> On Tue, Feb 5, 2013 at 6:12 PM, Chip Childers <chip.child...@sungard.com> >> wrote: >>> On Feb 5, 2013, at 6:10 PM, Marcus Sorensen <shadow...@gmail.com> wrote: >>> >>>> Well, for example, take >>>> https://issues.apache.org/jira/browse/CLOUDSTACK-644. It is >>>> 'unresolved', but the code was merged a few weeks back. It has had >>>> two subtasks for awhile. Do I close it, or do I wait because those >>>> subtasks are dependencies of the whole package? >>> >>> Please to keep it open. >>> >>> Sorry for the confusion, but I've been talking about maintaining >>> comments about status, as well as keeping the fix version accurate. >>> >> >> So closing the ticket doesn't close the sub-tasks - they are >> sub-tasks, not dependencies (or vice versa) >> >> --David > > Yes, I didn't think it would close the sub-tasks, but sub-tasks by > definition are things that need to be finished before completing the > task, no? Hmm, I think they are all distinct, and only really 'linked' to the issue of getting code in which seems complete, but perhaps I am wrong. --David
