Comment configurer heures et jours ouvrables ?

[Manuel.MAULINE]

---

Est-il possible de configurer de quelle heure à quelle heure s’étend un jour ouvrable sur jira ? Le problème se pose notamment dans le graphique de contrôle qui calcule le temps passé dans chaque état du workflow : je remarque que jira considère qu’un jour = 24h et ça fausse le résultat. 

Par exemple : si on considère que les développeurs commencent à travailler à 9h et arrêtent de travailler à 18h, une tâche commencée à 17h et finie à 10h le lendemain matin aura durée 2h. Mais pour jira, ça aura pris 17h. Alors que la même tâche commencée à 9h du matin et finie à 11h sera correctement comptabilisée à 2h de travail.

[Emre Toptancı _OBSS_]

Hello @Manuel.MAULINE ,

Sorry we can't respond in French but I hope my below answer in English can help you.

Jira's own Control Chart, Age and Created vs Resolved charts offer limited detail and flexibility.

If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this exact need. It is available for Jira Server, Cloud, and Data Center. 

Time in Status mainly allows you to see how much time each issue spent on each status and on each assignee. 

       

Time in Status offers two report types for your case:

The first one is Status Duration report (please see the screenshot above) which shows how much time each issue spent on each status. This report type has Consolidated Columns feature. This feature allows you to combine the duration for multiple statuses into a single column and exclude unwanted ones. It is the most flexible way to get any measurement you might want. Measurements like Issue Age, Cycle Time, Lead Time, Resolution Time etc.

As an alternative approach, Time in Status also has Duration Between Statuses report type which shows the duration between two specific statuses. This report type also allows the user the exclude the times for "pause" statuses.

  

All Time in Status reports supports custom calendars. That means you can define your custom work calendars with their own working days and working hours. Time in Status will calculate durations only spent in those calendar hours.

These reports show a list of issues by default so you can see the metric values for each issue separately. Also, for all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total cycle time per customer (organization) or average resolution time per sprint, week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints is particularly useful here since it allows you to compare different time periods or see the trend.

Time in Status calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well. It supports both Company Managed and Team Managed projects.

Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts.

And the app has a REST API so you can get the reports from Jira UI or via REST.

  

Using Time in Status you can:

• See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
• Calculate averages and sums of those durations grouped by issue fields you select. (For example, see average InProgress time per project and per issue type.)
• Export your data as XLS, XLSX, or CSV.
• Access data via REST API. (for integrations)
• Visualize data with various chart types.
• See Time in Status reports on Jira Dashboard gadgets

Timepiece - Time in Status for Jira

EmreT

[Walter Buggenhout]

Hi @Manuel.MAULINE and welcome to the Community!

In Jira Service Management (JSM) there are calendars available to configure SLA's. Jira Software does not have this functionality, but you should be able to work around the issue, simply by letting your developers track their time.

Out of the box, you can enter time based estimates in the Original Estimate field. By logging their actual time spent, you will be able to track how much time was really worked on each issue. The Atlassian Marketplace offers several solutions that let you extend Jira's native capabilities there, so you can even add calendars with working hours for your team based on these built-in time tracking priciples.

The Control Chart you refer to serves a different goal. It lets you track lead and cycle time for work that enters your teams. From that perspective it is important to track how many days it takes for work that enters the team until its completion. It does not matter how many hours are being spent for the chart to deliver its key information.

Hope this helps!