-
Notifications
You must be signed in to change notification settings - Fork 2
README: "open your issue against" #34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for pointing this out. I guess that when we say issue we mean issue report. One could argue that the term issue has become equivalent to the term ticket, which we used to use. Strictly speaking, you can also not open a ticket. Please go ahead and change the content so that it is better. |
Hi @wimjongman
An honour
In some instances, clearly.
Hum. Do you agree that a ticket can be closed?
I think the formulation I suggested (without the emphasis) would be fine. |
Yes, if you say that a Ticket now means a bug report. A ticket used to be something that you bought to get on a train or something ;). Semantics... 🗡️ |
"Ticket"
I wouldn't go that far as "ticket" didn't lose its original sense. But "ticket" can mean "issue report", or something very close to that (which I would basically describe as a recorded change request).
Indeed, but the word complexified a long time ago. You will find plenty usages of "(IT/support/helpdesk) ticketing system" online even from their creators, and out of 3 dictionaries I consulted:
And none of these indicate the sense as discouraged. I am convinced that "ticket" can be used as a quasi-synonymous for "issue report", but I do not recommend it over "issue report". |
Yes, I agree. |
The README's Reporting issues section ends with the following paragraph:
An issue can be introduced. solved or discovered, but not "opened" (as opposed to a ticket).
This should read something like:
By the way
The text was updated successfully, but these errors were encountered: