What's painful, it's not doing something repeatitive. It's being presured to repeat it, without being let automatizing it, which is what we should do as programmers.
She did the wrong thing and asked her boss. "Not enough time, there's more urgent things to do."
She then lost an hour per week, contributing to the general sense of urgency that she lived under. Of course, this wasn't the only such script she thought about by far.
-----
My advice: if you can shoulder the risk, automate it before your boss tells you not to.
I think programmers should be paid to not only do the crappy grunt-work, but also for automating it away, even though there will sometimes be cases where it turned out not to be worth it. To me, the automating is part of the job.
And sure, I remember when I used to think I could rewrite entire applications in a few hours the "right way", but that was pure inexperience on my part. For a junior dev, they might want to run it by someone more experienced, but otherwise, these kind of tangents can turn out to be some of the most valuable time spent on a project.
I agree, except no one should ever have to work on their own time. Personally, I think she should have written the script on company time.
So don't present your results to the boss until all the work's done. It takes as long as it takes.