2020.03.18
英文メールの書き方：バグの指摘に返信する
こんなシチュエーション、お仕事でありませんか？
ユーザーテストを実施する中、バグの報告があったので返信したい。
英文メールで「バグの指摘に返信する」お手本を動画でチェック！
こちらの動画では、伝えるべきメッセージとニュアンスを書き手が考えているところから、以下の内容のメールを実際に英語で書く様子までをご覧いただけます。
———————
ジョシュアさん、
バグを発見してくださってありがとうございます。
このような現象でしょうか：フォームに日付を入力しようとしたところカレンダーが現れた、しかしカレンダー内の日にちを選択できず、さらに閉じることもできなかった？
また、ウィンドウズとMacどちらを使用されていたのかと、どのブラウザー（たとえばChrome, Safari, Firefox）を使用されていたか教えていただけますか。
よろしくお願いします。
———————
今後の仕事での英語メールの参考になれば幸いです。
【動画内の”CC”ボタンをクリックして英語字幕を表示！】
【過去の動画を見るにはYoutubeページへ！Subscribe！】
0:00:05.460,0:00:06.460
Hello everyone.
0:00:06.460,0:00:07.750
Welcome to E-mail Picks!
0:00:07.750,0:00:10.660
Spring has come!
0:00:10.660,0:00:11.660
I feel it.
0:00:11.660,0:00:16.930
I was getting sick of wearing the same black
coat everyday.
0:00:16.930,0:00:22.000
Now I am leading a project to develop a new
online service and we are in the testing phase.
0:00:22.000,0:00:28.550
The development team has worked hard to put
together the IT system, and they have conducted
0:00:28.550,0:00:33.899
lots of testing to find bugs, but of course
we can’t find everything by ourselves, so
0:00:33.899,0:00:38.829
we are now asking people in different departments
to do a test run together.
0:00:38.829,0:00:43.420
So far we have received a comment from one
person, and he is reporting what sounds like
0:00:43.420,0:00:47.620
a bug, and now I need to report it to our
development team.
0:00:47.620,0:00:52.480
But to do that, I also need to know a few
things like what web browser he was using
0:00:52.480,0:00:56.710
and if he was using Mac or Windows.
0:00:56.710,0:01:02.429
So today, I’m going to write to my colleague
to thank him for reporting a bug and also
0:01:02.429,0:01:04.480
to ask him for more detail.
0:01:04.480,0:01:05.900
Here goes.
0:01:05.900,0:01:07.320
Hi Joshua,
0:01:07.320,0:01:10.200
We are grateful for your taking time to find
the bug.
0:01:10.200,0:01:15.500
So to confirm, is this right: when you tried
to input a date in the form, a calendar appeared,
0:01:15.500,0:01:19.520
but you were not able to select anything in
the calendar, and also you were not able to
0:01:19.520,0:01:20.840
close the calendar?
0:01:20.840,0:01:26.670
Also, could you let me know if you use Windows
or Mac and what web browser you were using
0:01:26.670,0:01:29.260
(e.g. Chrome, Safari, Firefox)?
0:01:29.260,0:01:30.430
Thanks so much!
0:01:30.430,0:01:31.430
Kyota
0:01:31.430,0:01:37.610
OK, so first, I started off by thanking my
colleague for reporting the bug, of course.
0:01:37.610,0:01:41.950
And now I needed to confirm what he meant
in his e-mail message.
0:01:41.950,0:01:46.920
Through working with the IT team for 2 months
now, I have learned a basic point that we
0:01:46.920,0:01:50.670
need to be able to replicate the bug in order
to fix it.
0:01:50.670,0:01:52.869
So I’m asking for details here.
0:01:52.869,0:02:00.700
And then I asked the browser my colleague
was using, and used the abbreviation e.g.
0:02:00.700,0:02:04.350
E.g. is what you write before you give some
examples.
0:02:04.350,0:02:08.250
It stands for something in Latin not English
so don’t bother,
0:02:08.250,0:02:09.789
So there you go.
0:02:09.789,0:02:13.120
An e-mail to respond to a bug report.
0:02:13.120,0:02:19.270
Actually we are not running into many bugs
so hopefully we can meet the launch deadline
0:02:19.270,0:02:21.250
without any new problems.
0:02:21.250,0:02:22.450
That’s it for today.
0:02:22.450,0:02:24.390
Thank you for watching and I’ll see you
next week.
Hello everyone.
0:00:06.460,0:00:07.750
Welcome to E-mail Picks!
0:00:07.750,0:00:10.660
Spring has come!
0:00:10.660,0:00:11.660
I feel it.
0:00:11.660,0:00:16.930
I was getting sick of wearing the same black
coat everyday.
0:00:16.930,0:00:22.000
Now I am leading a project to develop a new
online service and we are in the testing phase.
0:00:22.000,0:00:28.550
The development team has worked hard to put
together the IT system, and they have conducted
0:00:28.550,0:00:33.899
lots of testing to find bugs, but of course
we can’t find everything by ourselves, so
0:00:33.899,0:00:38.829
we are now asking people in different departments
to do a test run together.
0:00:38.829,0:00:43.420
So far we have received a comment from one
person, and he is reporting what sounds like
0:00:43.420,0:00:47.620
a bug, and now I need to report it to our
development team.
0:00:47.620,0:00:52.480
But to do that, I also need to know a few
things like what web browser he was using
0:00:52.480,0:00:56.710
and if he was using Mac or Windows.
0:00:56.710,0:01:02.429
So today, I’m going to write to my colleague
to thank him for reporting a bug and also
0:01:02.429,0:01:04.480
to ask him for more detail.
0:01:04.480,0:01:05.900
Here goes.
0:01:05.900,0:01:07.320
Hi Joshua,
0:01:07.320,0:01:10.200
We are grateful for your taking time to find
the bug.
0:01:10.200,0:01:15.500
So to confirm, is this right: when you tried
to input a date in the form, a calendar appeared,
0:01:15.500,0:01:19.520
but you were not able to select anything in
the calendar, and also you were not able to
0:01:19.520,0:01:20.840
close the calendar?
0:01:20.840,0:01:26.670
Also, could you let me know if you use Windows
or Mac and what web browser you were using
0:01:26.670,0:01:29.260
(e.g. Chrome, Safari, Firefox)?
0:01:29.260,0:01:30.430
Thanks so much!
0:01:30.430,0:01:31.430
Kyota
0:01:31.430,0:01:37.610
OK, so first, I started off by thanking my
colleague for reporting the bug, of course.
0:01:37.610,0:01:41.950
And now I needed to confirm what he meant
in his e-mail message.
0:01:41.950,0:01:46.920
Through working with the IT team for 2 months
now, I have learned a basic point that we
0:01:46.920,0:01:50.670
need to be able to replicate the bug in order
to fix it.
0:01:50.670,0:01:52.869
So I’m asking for details here.
0:01:52.869,0:02:00.700
And then I asked the browser my colleague
was using, and used the abbreviation e.g.
0:02:00.700,0:02:04.350
E.g. is what you write before you give some
examples.
0:02:04.350,0:02:08.250
It stands for something in Latin not English
so don’t bother,
0:02:08.250,0:02:09.789
So there you go.
0:02:09.789,0:02:13.120
An e-mail to respond to a bug report.
0:02:13.120,0:02:19.270
Actually we are not running into many bugs
so hopefully we can meet the launch deadline
0:02:19.270,0:02:21.250
without any new problems.
0:02:21.250,0:02:22.450
That’s it for today.
0:02:22.450,0:02:24.390
Thank you for watching and I’ll see you
next week.
