[#JRA-13202] Need the ability to change default working days.

JIRA

Need the ability to change default working days.

Created: 30/Jul/07 03:09 AM Updated: 10/Aug/07 12:13 AM

Component/s:

Time Tracking, Project Management

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Environment:

N/A

Participants:	Anton Mazkovoi [Atlassian], Christopher Van Kirk and Yaron Golan
Since last comment:	49 weeks, 1 day ago
Labels:

Description

« Hide

I need to have the ability to set the working days other than the default.

For example we (in Israel) do not work on Fridays but we DO work on Sundays.
In addition, we have our holidays which should consider as non working days while several other holidays which might be considered as a non working days are totally regular working days for us.

The meaning of lacking this feature is that I cannot keep accurate track of the time it takes to handle a bug reported to my Jira.
This makes the Jira less useful for our needs as a utility that supports project management.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 31/Jul/07 03:20 AM

Yaron,

Currently JIRA does not really make use of the weekend/workday information. If we allow to specify which days are work days and which ones are not, how will this help? I presume this information then will need to be used in other places.

Cheers,
Anton

[ Permlink | « Hide ]

Yaron Golan - 31/Jul/07 06:03 AM

Hi,
I guess that once the ability to specify which days are work days and which ones are not will be applied, I can do the rest by myself.
Is this feature feasible? will it be the the coming next releases?

Many thanks in advanced,
Yaron Golan
RADWIN

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 31/Jul/07 11:18 PM

Yaron,

At the moment the feature is not on schedule as we have a lot of features that customers are asking about:
http://jira.atlassian.com/browse/JRA?report=com.atlassian.jira.plugin.system.project:popularissues-panel

The policy for scheduling new features and improvements can be found here:
http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements

I also feel that if we start implementing features that do not really add any value without further customisations, a lot of cutomers will find that very confusing and will be very puzzled as to why the feature is even there.

Would you be able to provide more information as to how you are planning to use this feature. That is, what is "the rest" when you say "I can do the rest by myself".

Cheers,
Anton

[ Permlink | « Hide ]

Yaron Golan - 01/Aug/07 12:04 AM - edited

Hi,
The main idea of using this feature is for statistic reasons.
I'd like to have the ability to provide a report to my managers with the following information;

Which bug took the most / least time to solve
What is the average time needed to solve a bug (per component?)
Which user needs the most / least time to handle an issue.
Actual vs. estimated working time.
etc.

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 02/Aug/07 01:58 AM

Hi Yaron,

Thanks for the update. Are you using JIRA's time tracking feature? If so, I believe some information can be done without custom code:

Which bug took the most / least time to solve - it is possible to sort by the Time Spent column and hence get the issue that took the longest time
What is the average time needed to solve a bug (per component?) - you will need to make a custom report
Which user needs the most / least time to handle an issue. - you will need to make a custom report
Actual vs. estimated working time - the Time Tracking report might help with this:
http://www.atlassian.com/software/jira/docs/latest/timetracking_report.html

However, if you are writing custom code, would it be possible to have the custom code responsible for knowing which days are work days?

Cheers,
Anton

[ Permlink | « Hide ]

Christopher Van Kirk - 10/Aug/07 12:13 AM

All due respect and everything, but I'm glad I saw this before I bought your product. Good luck trying to sell this system in countries with irregular working periods.