Hi Gregg, we are trying to establish a process where this will never happen again - we do want to make sure that tickets are not forgotten/ignored. But we need to define a starting line for this. Once we have put Jira into a state where we only have tickets that are assigned or checked - we will make sure that tickets will be elevated in priority when getting older. There should be no ticket that has been not touched for 6 month.
Question is: What does it mean for a ticket if it has not been looked at for more then 6 month now - what is the reason that it has been ?ignored?. In most cases the problem is that the ticket is either to generic (like: lets remove all mem leaks) - or that there is no owner/assignee for it. Dave and George did a good start to look into these tickets - and I suggest that we should try to find owners for the important ones. thanks Christian On 23 Mar 2017, at 22:06, Gregg Reynolds <dev at mobileink.com<mailto:dev at mobileink.com>> wrote: On Mar 10, 2017 2:59 AM, "Christian Gran" <gran at lynxtechnology.com<mailto:gran at lynxtechnology.com>> wrote: Hi, there are currently 141 issues in Jira, that are in open state and have not been updated for more then 6 month now. The plan is to clean up Jira and close outdated tickets by end of March. wtf? so if i submitted a ticket 7 months ago, and it got ignored, you're proposing to just blow it away? am i misunderstanding what you propose? -g If you see a ticket, that you still want to keep - please just add a comment to it. This will update the ?updated date? field and it will no longer be part of the filtered tickets. For the list of tickets, please use this Jira filter: status in (Open, "In Progress", Reopened, Assigned, "To Do", "In Review") AND updated <= -180d or just this link https://jira.iotivity.org/issues/?jql=status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20Assigned%2C%20%22To%20Do%22%2C%20%22In%20Review%22)%20AND%20updated%20%3C%3D%20-180d<https://jira.iotivity.org/issues/?jql=status%20in%20(Open,%20%22In%20Progress%22,%20Reopened,%20Assigned,%20%22To%20Do%22,%20%22In%20Review%22)%20AND%20updated%20%3C=%20-180d> Please feel free to comment, or if you have some more input how we can make sure that we only keep issues in Jira we are actually working on?. thanks Christian _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> https://lists.iotivity.org/mailman/listinfo/iotivity-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170324/26eb33d6/attachment.html>
