Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#2032 closed change (fixed)

[trac issues 1] rename resolution "invalid" by "incomplete"

Reported by: philll Assignee: philll
Priority: Unknown Milestone:
Module: Infrastructure Keywords:
Cc: sebastian, trev Blocked By:
Blocking: Platform: Unknown
Ready: yes Confidential: no
Tester: Verified working:
Review URL(s):



The current term "invalid" as a resolution for issues that don't comply with our TracGuide sounds harsh as it could imply that the whole idea behind an issue is not valid at all. What we actually use it for, is more to show that an issue was reviewed and is regarded as incomplete.

What to change

In the issue tracker issues1, rename the resolution "invalid" by "incomplete".

Change History (3)

comment:1 Changed 6 years ago by philll

  • Resolution set to fixed
  • Status changed from new to closed

comment:2 Changed 6 years ago by sebastian

  • Cc sebastian trev added

First of all this change and it's purpose wasn't announced anywhere, not even in the notes of the meeting were this were supposedly decided. :(

Moreover, I'm not sure whether it is appropriate to replace "invalid" with "incomplete". Formerly we usually didn't close "incomplete" issues, but merely didn't set "ready" for those issues. If we are changing the workflow now, closing those issues as "incomplete", fine with me. But there are used to be issues, I were used to close as "invalid", but IMO doesn't really classify as "incomplete". Those are issues that are out of scope, like filter list issues and something that would have to be changed in the browser instead. And feature requests that are just not feasible regardless of how complete they were specified. For those issues I have two options now. Closing them as "rejected", however this would kinda imply that I deny a request that could theoretically be implemented but it can't. Or as "incomplete", however this would imply that the issue can be completed but it can't either.

comment:3 Changed 6 years ago by philll

I would be completely fine with having "invalid" in addition to "incomplete" to mark out of scope issues more obviously. @palant: Any thoughts?

Note: See TracTickets for help on using tickets.