| Title: | Connecting screen shots to stories or tasks |
| Summary: | How can people work *easily* with both screen shots and Rally? |
| Full Description: | One of the things I see our business people fighting when using rally
is not having a really simple way to work with screen shots. The
expectation: open word, paste a screen shot of an existing screen,
circle areas on the screen where they want a change, and type a few
lines of narrative. I'd love to see them do something so simple in
Rally where the result of their effort would be scheduled, tracked,
tested and released. Supposedly fogbugz can accept a screen shot. So
why not Rally? Alternately, a tool, technique, idea of ways to move really fast from screen shot to embedded image. Right now, we are just starting to get them to have many small word docs that are linked to the story. Better, but not best! |
| Browser Version: | Firefox 2.0 |
I agree that that is far too many steps to be useful.
I use Rally similarly to DanN when filing screenshots against a defect or user story. I also use a utility called Gadwin PrintScreen (Windows only) which allows you to rubberband an area of the screen and write it to a file or copy it to the clipboard easily. For those Windows users, you should check it out.