pre-publish worklog consolidation

I think what you're saying is consolidating somehow before sending the logs.

I wonder if outlining out workflow would be helpful --- so here goes:

work on task A and send for review.
while A is in review start working on B get to a stopping point and send for review
repeat this process for X number of tasks all which have time accrued against them.

at the end of the day, task A has come back from review with some changes so we start working on those changes (all the while applying time to it).

I think what you're proposing is a good intermediate step, but if we worked on task A in the AM and didn't get back to it until the afternoon, we'd like all time to be logged as one "chunk"

yes, you could argue the point that we should submit the time as soon as we've hit "stop timer". That would be a more accurate representation of when our work was completed, but in our case (i don't know if we'd be considered a "standard" user or not), i'm not sure the proposed solution would get us much.

What do you think @emilio?

I personally tend to bounce back and forth between tasks starting and stopping the log on different ones as I get to them so instead of sending a barrage of e-mails throughout the day I would rather do one big push at the end of the day. Of course, that ends up being a long list of e-mails that get sent at the end of the day instead.

I like both suggestions:

- auto-publish (as an option, and default to no)
- submit worklog at 3pm for 1.5 hr

Perhaps what would suit most applications would be an option to either combine only adjacent worklogs on the same issue, or combine all not-yet-published worklogs on the same issue (my case) so that only 1 email per issue will be sent by Jira. In the latter case, I like the idea to leave the final ending time intact and adjust the starting time, especially since it's the starting time too that can be adjusted manually during tracking.

I've worked with the new implementation for two days and I find it perfect! :-)

Thanks!