Hi Kartsten, this looks like a great project.
I noticed your comment here #1485910-4: custom backend plugin with no fields shows broken handler
"Fixed" means that something was actually fixed. In this case I think the appropriate status would be "closed (won't fix)".
Comments
Comment #1
kars-t commentedHi Tim
I am using "fixed" because to me the closing of an issue with an autotext might be seen as rude. If I used "won't fix" the issue would be immediately drop from the standard issue queue view.
So I think it is more polite to set the issue to "fix" and give them 20 days before it is automatically set to be closed.
But best would be if we get a new status like "Needs more input" that is given to any support issue that is older than 3 weeks. And than lets say 2 weeks later it is closed and set to maybe "Won't fix" or something new and nicer like "autoclosed".
I spoke to webchick about this at Bad Camp and she said I should approach the Webmaster team. I had this issue running and there are some crosslinks about this.
#1377678: Automatically close support issues after X days
#1193584: Auto closing of older issues
#156704: Dealing with "postponed (maintainer needs more info)" issues
I will tackle those issues again.
I think "won't fix" is indeed the better fit but will gather more input if "won't fix" is rude or not. Stay tuned and hope to speak to you in Portland.
Comment #2
colanI'm adding my support for "won't fix" or some other non-"fixed" status as "fixed" is simply incorrect.
Comment #3
kars-t commentedChatted with YesCT about this and she says the same as you two. I make a patch asap.
Comment #4
kars-t commentedCommited the "won't fix" status and tested it :)
Thanks all!