Hi, We have a growing problem with Jira issues forgotten in the "In Progress" state. For the 10 most important Jira projects we currently have 600+ issues being stuck in the mentioned state. Since we recognize "In Progress" as a blocking state (not open for take over by other engineers), I believe we should keep the numbers small and mostly constraint to limited time frames.
By historical standard this is still much better than past times and I attribute most of it to the "Fixed" git tag which automatically closes Jira issues. Nevertheless of those "In Progress" issues about 170+ have not been touched (or were forgotten) for more than 3 months. I would like to do something about this by adding some automation similar to the "Need more Info" automation. Those forgotten issues are likely not in progress anymore or were fixed a long time ago. I believe returning them to the "Open" state would trigger a re-evaluation by assignees (you). You either close them as already done or keep them in "Open" as you recognize them as not being done yet. My proposal would be to return every "In Progress" issue to "Open" if there was no change for 3 month. I'd appreciate your feedback. -- Alex _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
