āRegressionā can be one option
āoperational challengeā
Funny how, the last time this ābugā occurred was exactly 1 year ago, and the firm that supplies the system used the same wording.
They donāt like the word bug because some of what is reported is a problem with configuration as opposed to a programmatic glitch⦠but they donāt know 'til they triage. This is a mixed environment where some of what is being tested is new code, some is configuration and customization for several new software packages ā like a fruit salad, really.
AND THE ANSWER WASā¦
issue
Yes, after debate and several alternatives considered, they like the generic term issue the best.
(I still rather like hiccup myself)
Thanks for sharing the outcome of what they went with and for starting this conversation.
Good to explore these things with the community.
Hi Tracy, just curious but your original post said you couldnāt use issue because of Jira. Did you find a solution for that? Thanks
I suggest you to look at the last 3 comment before yours.
- Glitch
- Quirk
- Error
- Fault
- Anomaly
- Issue
- Flaw
- Imperfection
The terms ābugā, āfeatureā, etc. are surprisingly subjective. Iāve always seen items as either something that needs to be done, or something that doesnāt need to be done. The label has not mattered much in my opinion and experience.