In the bar below the menu the bugs assigned to the user and reported by the user are split into open and closed. What determines when a bug becomes closed? As far as I am aware all of the bugs entered so far are open (we have only been running one day), but one of the bugs I have reported is indicated as closed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmmm - that's what I thought. This looks like it might be a bug then, as none of the bugs that are now showing as closed actually have that status. I'll do a bit more investigation before reporting it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK, I've worked out what is happening and it's simple enough. In include.php the constant OPEN_BUG_STATUSES is defined. By default it is the 4 statuses that can be setup in the configuration (BUG_UNCONFIRMED, BUG_PROMOTED, BUG_ASSIGNED, BUG_REOPENED). If you add any new statuses that should be considered as opened the status_id for each needs to be added to this list. It would be nice if you could specify whether a status should be treated as open or closed when it is created. I'll give this some more thought.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yeah, an idea would be to have it configurable in the admin interface
whether a status is a closed or open type, then modify the other queries
based on that configuration.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In the bar below the menu the bugs assigned to the user and reported by the user are split into open and closed. What determines when a bug becomes closed? As far as I am aware all of the bugs entered so far are open (we have only been running one day), but one of the bugs I have reported is indicated as closed.
A bug is closed when the Status field has been changed to Closed.
Hmmm - that's what I thought. This looks like it might be a bug then, as none of the bugs that are now showing as closed actually have that status. I'll do a bit more investigation before reporting it.
OK, I've worked out what is happening and it's simple enough. In include.php the constant OPEN_BUG_STATUSES is defined. By default it is the 4 statuses that can be setup in the configuration (BUG_UNCONFIRMED, BUG_PROMOTED, BUG_ASSIGNED, BUG_REOPENED). If you add any new statuses that should be considered as opened the status_id for each needs to be added to this list. It would be nice if you could specify whether a status should be treated as open or closed when it is created. I'll give this some more thought.
Yeah, an idea would be to have it configurable in the admin interface
whether a status is a closed or open type, then modify the other queries
based on that configuration.