I'd like to revamp and simplify the Tickets modules used by this project. I'm outlying my proposals below. Does anyone have any thoughts on this?
There are currently three trackers set up: "Feature Requests", "Bugs" and "Patches".
Patches
Having trackers for "Bugs" and "Feature Requests" makes sense. I'm not so sure about "Patches". To my mind, a patch should be submitted to fix a bug or add a feature and should be added to the appropriate ticket on those trackers. Therefore I propose removing the "Patches" tracker.
Feature Requests
I propose simplifying the options in the "Status" field as follows:
Current Options
Proposed Options
Open
Open
Unread
Verified
Accepted
Closed-Fixed
Pending
Closed-Cancelled
Closed
Wont-fix
A request would start as "Open". Only at the point that the project has agreed that the feature is a valid request and should be developed would the status be changed to "Verified".
The "Priority" field currently accepts integer values from 1 - 9, with 5 as the default. I propose simplifying this to "High", "Medium" and "Low" with "Medium" being the default.
Bugs
I propose simplifying the options in the "Status" field as follows:
Current Options
Proposed Options
Open
Open
Unread
Verified
Accepted
Closed-Fixed
Pending
Closed-UnableToReproduce
Open-fixed
Closed-NotABug
Closed
Wont-fix
Closed-fixed
Closed-rejected
Similar to "Feature Requests", the bug would start as "Open" and only be changed to "Verified" when the project has confirmed that the issue is a bug that needs to be fixed.
The "Priority" field currently accepts integer values from 1 - 9, with 5 as the default. I propose simplifying this to "High", "Medium" and "Low" with "Medium" being the default.
The "milestone" field is currently used to determine whether a ticket is a "Bug Report" or an "Enhancement Request". I see this as redundant - enhancements should be on the "Feature Requests" tracker.
Support
I propose adding a new tracker called "Support". This would have the following statuses:
Open
Pending-confirmation
Closed
The ticket would stay at Open until a solution to the issue had been offered. At this point, it would be changed to Pending-confirmation until the user either confirmed the solution worked at which point it would be closed, or if more work was required, it could be changed back to Open.
I don't see any need for a "Priority" field on this tracker.
I also suggest setting this tracker as the "Preferred Support Page", as mentioned on the "Support" tab of the project.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'd like to revamp and simplify the Tickets modules used by this project. I'm outlying my proposals below. Does anyone have any thoughts on this?
There are currently three trackers set up: "Feature Requests", "Bugs" and "Patches".
Patches
Having trackers for "Bugs" and "Feature Requests" makes sense. I'm not so sure about "Patches". To my mind, a patch should be submitted to fix a bug or add a feature and should be added to the appropriate ticket on those trackers. Therefore I propose removing the "Patches" tracker.
Feature Requests
I propose simplifying the options in the "Status" field as follows:
A request would start as "Open". Only at the point that the project has agreed that the feature is a valid request and should be developed would the status be changed to "Verified".
The "Priority" field currently accepts integer values from 1 - 9, with 5 as the default. I propose simplifying this to "High", "Medium" and "Low" with "Medium" being the default.
Bugs
I propose simplifying the options in the "Status" field as follows:
Similar to "Feature Requests", the bug would start as "Open" and only be changed to "Verified" when the project has confirmed that the issue is a bug that needs to be fixed.
The "Priority" field currently accepts integer values from 1 - 9, with 5 as the default. I propose simplifying this to "High", "Medium" and "Low" with "Medium" being the default.
The "milestone" field is currently used to determine whether a ticket is a "Bug Report" or an "Enhancement Request". I see this as redundant - enhancements should be on the "Feature Requests" tracker.
Support
I propose adding a new tracker called "Support". This would have the following statuses:
The ticket would stay at Open until a solution to the issue had been offered. At this point, it would be changed to Pending-confirmation until the user either confirmed the solution worked at which point it would be closed, or if more work was required, it could be changed back to Open.
I don't see any need for a "Priority" field on this tracker.
I also suggest setting this tracker as the "Preferred Support Page", as mentioned on the "Support" tab of the project.
I think these changes will make the process simpler. Thank you for leading the way!
I'm starting this work now. I'll post again when it's complete...
OK, I think that's everything done. As we start using it more, we might find things that need "tweaking", but we'll see how we get on.
If you do find anything that's not working how you think it should (or you think of anything that could be improved), please let me know.