+1
Under review

Suggestions for Bug status and others

Eldo John 9 years ago updated by tech 8 years ago 2

The following some suggestions.


1. Addition of 'duplicate' to Bug status.

- In case a user finds it to be a duplicate to the existing bug.

2. Default Bug list view

- The bug list should show the by default all the existing bugs for a project which further can be further be filtered to bug status.

3. Report Bug functionality in the dashboard for a project.

4. Bug Ids for each bug reported.

- helps in easy tracking of bugs.

5. The following functionality should not be extended to a developer.

a. Delete a bug assigned to him/her by others.

- In this case a developer can delete a bug which relevant and create a issue in tracking the bug assigned to them.

b. 'Closed' functionality of Bug status.

- This function should be extended to the testers alone after resting the bug.


Also tester should be able to reopen a bug if encountered again.

Under review

1. Not everyone wants a duplicate bug status. I'm not sure if it makes sense to add it as a default status. If people vote for it, we'll do it.

2. That is how the bug list currently works.

3. We've now added this.

4. All bugs have a numeric identifier.

5. We're close to releasing a complete overhaul of the permissions system that addresses this.


Thanks!


Simon