sojrner
2015-10-02 22:35:43 UTC
Hello All,
I've been running Agilo on Trac for about 6 months now and we've
encountered an issue with the flow when tickets close. Currently when a
ticket is closed, any remaining hours are set to zero. When reporting on
hours after a ticket is closed results in inflating the report results.
Specifically it inflates the hours of the user that closed the ticket, but
the hours also log against the milestone in general. I am aware of
the CloseTicketWithRemainingTimeZeroRule, which I'm using for different
reasons. I'm also wondering if there is another rule that allows the
feature of setting hours to zero on close (the near-opposite of the other
rule) to be turned off as well. If not, can anyone suggest an alternative?
Let me know if this is at all unclear or if I can supply further
information. I've spent quite some time searching for an answer to this to
no avail. Thanks in advance for the response and help.
--
--
Follow Agilo on Twitter: http://twitter.com/agilofortrac
Please support us by reviewing and voting on:
http://userstories.com/products/8-agilo-for-scrum
http://ohloh.net/p/agilo-trac
http://freshmeat.net/projects/agiloforscrum
You have received this message because you are subscribed to
the "Agilo for Trac" Google Group. This group is focused on
supporting Agilo for Trac users and is moderated by
Agilo Software GmbH <http://www.agilosoftware.com>.
To post to this group, send email to ***@googlegroups.com
To unsubscribe from this group, send an email to
agilo+***@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/agilo
---
You received this message because you are subscribed to the Google Groups "Agilo for Trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email to agilo+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I've been running Agilo on Trac for about 6 months now and we've
encountered an issue with the flow when tickets close. Currently when a
ticket is closed, any remaining hours are set to zero. When reporting on
hours after a ticket is closed results in inflating the report results.
Specifically it inflates the hours of the user that closed the ticket, but
the hours also log against the milestone in general. I am aware of
the CloseTicketWithRemainingTimeZeroRule, which I'm using for different
reasons. I'm also wondering if there is another rule that allows the
feature of setting hours to zero on close (the near-opposite of the other
rule) to be turned off as well. If not, can anyone suggest an alternative?
Let me know if this is at all unclear or if I can supply further
information. I've spent quite some time searching for an answer to this to
no avail. Thanks in advance for the response and help.
--
--
Follow Agilo on Twitter: http://twitter.com/agilofortrac
Please support us by reviewing and voting on:
http://userstories.com/products/8-agilo-for-scrum
http://ohloh.net/p/agilo-trac
http://freshmeat.net/projects/agiloforscrum
You have received this message because you are subscribed to
the "Agilo for Trac" Google Group. This group is focused on
supporting Agilo for Trac users and is moderated by
Agilo Software GmbH <http://www.agilosoftware.com>.
To post to this group, send email to ***@googlegroups.com
To unsubscribe from this group, send an email to
agilo+***@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/agilo
---
You received this message because you are subscribed to the Google Groups "Agilo for Trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email to agilo+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.