Hello All,
There is a table in the page which is pre-populated. The table has a check box to approve/reject each row item and there are buttons (SAVE, CANCEL) in the page to save the changes and to cancel the changes.
A BUG saying "if there are no data in the table, then the SAVE and CANCEL button should be hidden" is raised.
Is this really a BUG or a SUGGESTION? How should i consider it?
EDIT: No such thing(button hide/disable) is mentioned in the SPEC
I would say a suggestion, but that really depends on your UI guidelines (if you have any).
Generally speaking, you disable the buttons, not hide.
Depends on your specs. If you specs states that the buttons should be hidden, then it's a bug - If there's no such mention in the spec it's a suggestion (or feature request)
I would say that's not a bug (and thus a suggestion), unless you there is a specification somewhere that says that hiding the buttons when there's no data is what should be done.
Nevertheless, I would suggest hiding the entire table with buttons and all saying "There's no data available" instead of just hiding the buttons.
A BUG saying "if there are no data in the table, then the SAVE and CANCEL button should be hidden" is raised. Is this really a BUG or a SUGGESTION?
If it's not addressed in the design document, then it is a feature request.
If the screen failed to load because of no data being present, or clicking either of the buttons resulted in an error - I would categorize that behavior as a bug. Feature requests are lower on the priority than bugs - if you're dealing with anything else on the page, make the necessary changes. Otherwise, leave it to the clients discretion to determine if this is to be included in the current release or put off until the next one depending on the current state of the pending release.
Personally, I would never disable a cancel button - that's the point, to allow the user to exit the given action without changing anything.
Many would see it as a suggestion if it is not explicitly specified in the design/spec.
However, with no explicit rule, one has to imply the "expected behaviour" from existing standards and conventions. The prevailing convention is that under these circumstances the buttons should be disabled. Therefore I would personally consider it a bug (an oversight in the implementation which leads to a sub-standard product).
It all depends on whether you want to produce a quality application, or simply bang out something quickly that your customer will pay you for.
I can sort of agree with the previous answers that if it's not mentioned in the spec, it's not a bug. But part of me says that this is a functionality that is so obvious that it should not need to be in the spec. (At least my) common sense says that if there is nothing so save, the save command should not be available. From that perspective, I would personally consider it a bug, not a feature request.
I'd call it an Issue - then you don't need to get too hung up on the grey area between a Bug and a Suggestion.
You usually only need to distinguish bugs from suggestions when there's a non-technical reason to do so (e.g. bug fixes are free, changes are chargeable). And in that case it's really more of a commercial issue subject to negociation.
A software bug is the common term used to describe an error, flaw, mistake, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways. The tester will check it with reference to SPEC.
In the above case if (button hide/disable) is not mentioned in SPEC then it is not a BUG but rather a Suggestion itself.
According to me the buttons should be disabled if the table is empty. If you make any changes in the table then only the button should be enabled.