jira software log time minutes

[Manu G]

How can i configure a project to allow me indicate number of minutes to complete instead a expiration date?

[Petter Gonçalves]

Hello Manu,

Welcome to Atlassian community!

Can you please let us know if you are using JIRA Server or Cloud?

I understand that you would like to have a countdown timer just like the SLAs of JIRA Service Desk, so you could see how many minutes you still have until the expected resolution time of the issue. Is it correct?

Unfortunately, JIRA Software does not have this kind of functionality, however, you can use some plugins to achieve it.

- For JIRA Server, we have the third-party add-on Time To SLA that allows you to build SLAs for your JIRA Software issues.

- For JIRA Cloud, You can use Tick Time Tracking for Jira that provide you timers to track your progress on issues.

Let me know if this information helps.

[Jack Hunter _HeroCoders_]

Hello @Manu G,

If by any chance you are referring not to SLA but "remaining estimate" concept then it is available in Jira: https://confluence.atlassian.com/jirasoftwarecloud/configuring-estimation-and-tracking-764478030.html 

It basically requires you to set the "original estimate" for an issue (in minutes/hours/days/weeks) and then log time against the issue and watch the progress and remaining time.

There are also plugins that allow you to track time automatically so you don't have to log work manually.

Clockwork Automated Timesheets allows you to record time worked by starting and stopping timer manually (with Start/Stop button) as well as record the time automatically, when the issue is moved through workflow like Open (time not tracked) => In Progress (timer ticking) => Done (timer stops and logs time). 

Cheers,
Jack

[Manu G]

Hi.

For the moment i am using Cloud but i am planning to use the server.

Let me explain our scenery and tell me how can i arrange everything at Jira software:

I have several type of tasks:

1. Order fulfilment. We need to log times of prepare orders.

By example we have 100 orders to prepare, if everything ok this task will be completed and passed to done column. 

 1. We need to register a number of orders prepared and orders shipped and study this number at analysis to see when task are not fully completed with all orders shipped.

 2. We need to register estimated time and completion time to study relationship at the analysis. To do this is time consuming to our workers because they need to be registering this information, each time they finnish a task, do you know the way to make this less stressing and more easy for our workers?

Thank you for your help.

Regards

[Jack Hunter _HeroCoders_]

It seems like the Jira time tracking (original estimate, remaining estimate, log work) should work for you. Here is how to:

• enable Jira time tracking
• use Jira time tracking

Clockwork can ease the pain when comes to logging work (registering time worked). It starts the timer when an issue is moved to In Progress, and next stops the timer when you move the issue to Done column. The time spent in between is logged to Jira worklog and reduces "remaining estimate". It all happens automatically so there are only two manual steps in the process:

• estimate the issue/task at the beginning (it these are repeatable tasks then you can probably keep/copy the estimation)
• analyze the "remaining estimate" and other tasks on the way to complete the project. You can use Jira reports for that purpose or Clockwork timesheets

You can also consider tracking the orders as a sub-tasks and watch which are completed or not with simple JQL or Jira Software reporting (e.g. for Epic, Spring or Version). 

In Jira, there are truly many possible ways.

I hope it helps.

Cheers,
Jack