Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

it's quite likely the discussion started with a simple question like "is this what should happen?" and blew up from there, the ticket being created only later. Yes, the email exchange should be included in the ticket, but it's quite normal for the ticket to come after the email exchange (usually as a result of the email exchange).

jwenting
– jwenting

2021-10-20 08:45:54 +00:00
Commented Oct 20, 2021 at 8:45
Actually, even if the email was the wrong channel, you're right in pointing out that, hopefully, a ticket tracker is used... And in that case, they might as well just add the email as a comment or an attachment of the ticket and reference the ticket. Simple enough. It's not necessarily as future-proof as having the reference material local to the codebase, though, but good enough for many cases.

haylem
– haylem

2021-10-21 00:25:50 +00:00
Commented Oct 21, 2021 at 0:25

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »