Why do people create issues without comment/description ...? :-(

[nelsonic]

does anyone think that creating an issue without a comment is enough to capture what is required...?

[sohilpandya]

Issues can be created at different stages/times of the day/project.

For me if they are created first thing in the morning, it'd be understandable to have descriptions attached to them. But what does one do if it's literally the end of the day?

• If the idea behind creating an issue is to capture an idea/next steps then at least that's been captured and the appropriate additions can be made to it when the person returns to it (they've planted the seed and they know where to begin when they return to the desk - next day/after lunch/after the weekend)

[nelsonic]

@sohilpandya you make a valid point, people may be at the end of their day and need to make a "note" of what to do next without going into detail.

I guess I'm just not used to seeing an email with only a subject line and a blank body. It feels incomplete/rushed...

My concern is that it's not an occasional occurrence limited to the circumstances you've described (which are valid!) I see F&C people post "incomplete" issues way too often and/or start working without putting enough thought into the requirement/user-story before hand.

We need to improve our process and encourage people to finish their day earlier in order to have time to consider what needs to be done next and ensure that the next issue they pick off (or add to) the backlog is well described and validated the day before it gets worked on. (there is empirical evidence to support this workflow as it allows your "unconscious" mind to deliberate on the question/challenge ahead of tackling it the following day...)