It's probably fine, if you put it in a separate section, clearing indicating that you are guessing.
At work we have an optional "diagnostic" section in our ticket template, mainly intended for the team, but I'd be happy to see a user try to fill it. At worse it's harmless, at best it gives the actual reason, somewhere in the middle it can give ideas even if it is wrong.
I wish. It happens very often that such speculation derails the whole investigation. It really shouldn’t, but people are people. If the title of the bug report says that the foobar is broken it might take weeks until someone realises that they were wrong and actually the problem is in the frobnicator which feeds the foobar.
Especially when because of this we assing the investigation to the wrong team. The foobar people don’t want to appear as if they don’t take the bug seriously, but all they check everything looks normal on their side.
You know, it just occurred to me that the "How to ask questions" document is targeted as much at hackers and how they should maintain their "standards" than at users who are asking questions. For example, the document has approving examples of "logically impeccable but dismissive" hacker answers; these make more sense as instructions on how a hacker should respond than as something relevant to a user.
I guess my point is that I had read the "How to ask questions" document for decades and viewed it as an objective document, not realizing how arrogant and "gatekeeping" it is.
Desperate for something to feed my jones, I snaffled my other sister's
abandoned flute. And wow! I was a natural...immediately better with it than
with the guitar I'd been hacking at for months. [...] This was delightful but
mystifying. All I'd had to do was learn to play a scale, and this amazing river
of music poured forth with barely an effort on my part. It seemed almost as
though my hands and lips had always known what to do, had been waiting for me
to pick up the flute. [...] I got these stunning rushes of pure timeless joy,
when my consciousness seemed to expand outwards from the limits of my skin to
fill the universe and I could no longer tell whether I was playing the music or
the music was playing me. Nor were these effects just going on inside my own
head. [...] I was walking home, idly puzzling over this peculiar incident, and
damn near fell over when I finally got it. That girl had been trying to cope
with a theophany; she had looked at me and seen a god. A particular god. And I
knew, suddenly, with utter shattering certainty, which one it was. And that it
probably was not the first time I had inadvertently triggered such an
experience, and would almost certainly not be the last. [...] Not that I took
any of it seriously as a description of the real world. It was an intellectual
chew-toy, perhaps at best a way of understanding the pathologies that prevented
human beings from living the infinitely more desirable life of reason and
science. Until I realized, finally, belatedly, what had been happening to me.
Until the Great God Pan reached out of my hindbrain and thundered "YOU!". And
his gift is music and his chosen instruments the pipes and flutes. And his, too
the power of joy; magic so strong that when it flowed out of me, even before I
knew what I was doing, it amazed people into awe and incoherence and poetry.
[...] (And, oh, yes. The first time I handled a set of pan-pipes I could play
them. Fluently. Effortlessly. And knew I could before I touched them.)
STEPS TO REPRODUCE Open foo click bar
EXPECTED RESULT saves bar
ACTUAL RESULT crashes with error x912344
MISC <any other logs, details here>
is the best. It gives just the right amount of detail to get started, in a good, actionable format.
Summary :
Steps to reproduce :
Expected result :
Actual result :
Build/Version :
And a few more fields about platform, severity, etc. on Jira.Out of curiosity, what does deving for Warner Bros mean? Like working on their internal systems and stuff? Netflix integrations or something? Sounds cool, bet you get to see movies before they come out too!
I was working at their Montreal Studio. It's exclusively a video game studio. I was mostly working in QA on Middle-earth: Shadow of War.
Even if the game is technically developed by Monolith Productions, Warner Bros. Interactive Entertainment (WBIE) helps with their ressources (Artists, QA, Devs).
There's also alot of internal tooling for Builds automation, Automated testing / QA Aids tools, etc that is handled by WBIE as the game editor.
We didn't see movies before they got out but we had access to a 30-50 persons theater room that I was able to "rent" for free outside of business hours to watch movies with friends and show them the non-secure areas of the office. (Cafeteria (Free drinks!), gaming room, etc.))
I'm not really into commics but we had a room with thousands of comic books that we could take and read anytime we wanted (WB owns DC Entertainment).
I worked there 6-8 months when I was out of school before getting my first dev job.
Users tend to rename programs, even give them names of other programs. Our entire finance department can't wrap their heads around the fact that 'Oracle' is not a bookkeeping application. Worse, they are now convinced the new version is called 'fusion'. Oracle financials? Never heard of.
1. When I do this
2. Here is what I expect to happen
3. But instead, this happens
If it's good enough for my colleagues to submit tickets like this, it's good enough for me!
Get a good set of steps for reproducing the problem, but wander a little off those steps to see what is actually necessary. I've been surprised more than once when something that I thought was incredibly complex only required a few steps. And also been surprised when a complex repro was actually complex (e.g., if I drag quickly it works, but if I drag slowly it doesn't? what?).
> GitHub and GitLab support task checklists in Markdown and also project boards [...]
> GitHub and GitLab support (multiple) Issue and Pull Request templates:
> Default: /.github/ISSUE_TEMPLATE.md || Configure in web interface
> /.github/ISSUE_TEMPLATE/Name.md || /.gitlab/issue_templates/Name.md
> Default: /.github/PULL_REQUEST_TEMPLATE.md || Configure in web interface
> /.github/PULL_REQUEST_TEMPLATE/Name.md || /.gitlab/merge_request_templates/Name.md
> There are template templates in awesome-github-templates [1] and checklist template templates in github-issue-templates [2].
So I start it off with a few brief paragraphs of text explaining what I did, what happened and what I expected to happen. Each paragraph only a couple of sentences long.
Then below that I fill in with more details.
Of course this still means that if you glance at it you still see a lot of text and may not bother reading. But my hope is that if by chance the recipient does read the first few paragraphs then it will provide the necessary motivation to either read on or to begin investigating on their own.
1. config and versions
2. the bug (failure to see expected results
3. how to reproduce in as simple terms as possible
4. any data such as screen shots, core dumps, logs, etc