Hi everyone -

If you use all the workflow states, a simple fix generates these emails:

[jira] created
[jira] commented (n times - maybe, but n can be 0)
[jira] assigned
[jira] Work started:
svn commit:
[jira] Work stopped
[jira] Resolved
[jira] Closed

I propose we reduce our email reading load slightly by eliminating some of the jira workflow when it seems less interesting.

For instance, for things which are quick to do - skip the Jira "Work started"/ "work stopped" updates. And when you "resolve" an issue, do you also need to "close" it? (The velocity project seems to "resolve")

-Marshall

Reply via email to