JIRA: what does start and stop progress buttons do ?

[wajdhaikal]

If an issue is stopped, then the timer won't calculate late days?

[Jakub Pierzchała · Accepted solution]

As far as I know they are only to trasition the issue throught hte workflow. This allows your manager to see what are his people currently working on.

This does not log your work automatically. You will need to log it in manually

[wajdhaikal]

then if estimated time which was set on creation is 3 days, and on day 2 I stopped the issue for 5 days then start it again. How I or my manager will know this issue is late? is there any indicator or icon to say this issue has took more than the estimated time? can I generate a report to show late tasks? based on estimated time field?

[Deleted user]

It depends what is he trying to achive.

If he wants to make sure that for the note is finished on the day you estimate you'll resolve it either he or you should set the "Due date" field. Issues due or overdue will appear in numerous places.

If he wants to see issues that were not estimated accurately (you estimated 3 days but it took you 2 or 4) he should use the Time tracking report for the project

[Jakub Pierzchała]

It depends what is he trying to achive.

If he wants to make sure that for the note is finished on the day you estimate you'll resolve it either he or you should set the "Due date" field. Issues due or overdue will appear in numerous places.

If he wants to see issues that were not estimated accurately (you estimated 3 days but it took you 2 or 4) he should use the Time tracking report for the project

[Nic Brough -Adaptavist-]

Just to be clear - start and stop progress have nothing to do with estimates or timetracking, they change the status of the issue. Worklogs are the thing that feed back into the estimates.

Jakub's answer about the use of due-date and time tracking reports is what you need.

[rozuan]

how to log on work when start and stop progress? thanks

[Gebsun]

You can try following plugin https://marketplace.atlassian.com/plugins/com.gebsun.plugins.jira.startwork

[Nic Brough -Adaptavist-]

Add the "log work" field to the start/stop transition screens is a better approach

[Nic Brough -Adaptavist-]

It's excellent for automating logging work, but a lot of us don't work like that.

[Gebsun]

What if your transition does not have a screen? Adding one only for a log work is not a comfortable solution and you still have to remember/think of how much time you worked on an issue.

[Gebsun]

If you want default workflow actions to log work time autmatically you can try Automated Log Work plugin. It allows to integrate JIRA workflow actions like Start/Stop Progress, Close, Resolve with time tracking and log work automatically.

[Danny McArdle]

wajdhaikal

You could call a custom screen that set start dates when you press start Progress so you can track the start date of an issue. Then on pressing stop progress button you could call a another customer screen forcing the developer to enter in their time spent. This will keep the transition through the work flow and you can time track issues based on start date and time spent. Then to resolve an issue you can also call the custom screen to log time spent. You will have a full view of time spent on an issue there after.

[rozuan]

how to log on work when start and stop progress?

[Marco Antony]

In order to really have a transparent workflow "stop progress" should rather set the status of the issue to something like "on hold" instead of setting it back to "open". Even if the work on this issue is 90% done it looks like nobody touched that issue yet. Is there any way how I could change the status Jira is setting when pressing the "stop progress" button?

[Nic Brough -Adaptavist-]

Yup, edit your workflow, add a new status to it, repoint "stop progress" to that status, add a transition for "restart progress" back into "in progress" and you're done.

[Renjith Pillai]

If you use the Transistions plugin then you can actually see the time in the 'In Progress' state. But like Andy says, this has no relation to the work logged in the issue.

[Andy Brook [Plugin People]]

I use 'start progress' to indicate which tasks are current receiving attention, manager or no, the consequence is the same, information to others about what you're doing. Start/Stop progress has nothing to do with logged time against the issue, worklog management is separate.

[Nic Brough -Adaptavist-]

They move the issue through the workflow. I don't know what you mean by "timer".