[#JRA-14733] Time Spent is not available as a "screen" field

JIRA

Time Spent is not available as a "screen" field

Created: 31/Mar/08 11:24 PM Updated: 02/Apr/08 07:37 PM

Component/s:

Time Tracking

Affects Version/s:

3.12.2 Enterprise

Fix Version/s:

None

Time Tracking:

Not Specified

Environment:

Issue Links:

Duplicate

This issue duplicates:

JRA-868 Resolve & Time spent

Participants:	Anton Mazkovoi [Atlassian] and Tom Miller
Since last comment:	6 weeks, 2 days ago
Company:	pidi.com (Find related issues)
Resolution Date:	01/Apr/08 11:27 PM
Labels:

Description

« Hide

If you can't prompt the person using the system on a transition screen to put in the time spent on what ever they where working on, you really have a serious flaw when it comes to even the most basic of time and billing systems. Why you spent the time to make the "Time Tracking" field available which looks for the estimate is beyond me. I am glad you have it so we can use it on our LOE transition, but this is a serious over site on your part. This needs to be remedied immediately for Jira not to be a complete waste of time from the work log point of view. I hand not realized that this was a problem until after we purchased the product. Please fix immediately.

There are other issues with work log and I will either create new or add to the existing tickets, but this over site should be fixed immediately. From what I can tell, it shouldn't be difficult to make this field available to put on screens, specifically transition screens.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 01/Apr/08 11:27 PM

Hi Tom,

It is not possible for us to add Time Spent as a separate field to the Issue Screens, as Time Spent is a read only field, that should only be updated by logging work against the issue (or editing or deleting issue work logs). Allowing users to manually update the Time Spent field would create inconsistencies in the data that would allow for more bugs to creep in.

I do agree that JRA-868 would be a useful addition to JIRA and we would like to implement it in the future. Unfortunately, at the moment I do not have an implementation date for this feature.

Choosing features for JIRA is the most difficult part of our jobs. We have to prioritise between a large number of possible suggestions, and ensure that we take into account various points of view across all of our customers.

At the moment we are working on adding 2 of the most popular feature requests to JIRA 4.0:

Adding ability to Share Dashboards (JRA-2509)
Import Project (JRA-1604)

The roadmap for JIRA 4.1 has not been finalised yet.

Please have a look at the following document for more information on the way we schedule new feature and improvements:
http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements

Please vote for JRA-868 as this is the best way for us to be able to track your interest in this feature.

Cheers,
Anton

[ Permlink | « Hide ]

Tom Miller - 02/Apr/08 08:45 AM

I appreciate the openness of your process. Sometime you add a feature that is nearly worthless because you missed something in the original design. This is the case here. If you make it difficult for the troops to put in their time, they more then often won't or will do it much later and take wild ass guesses. I have asked for lots of things from Atlassian in the way of capability and have worked with your excellent staff to find a work around, sometimes painful, but mostly effective. This isn't one for those instances and I am hoping to see this in 3.12.4, I feel it is that important!!!!

Is there a way to sponsor a feature? What if 100 of your customers put some money toward this feature to get it sooner then later? I feel it is that important!!!

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 02/Apr/08 07:37 PM

Hi Tom,

Thank you for your feedback and your kind words! They mean a lot to us!

We implement features and improvements in JIRA only in major releases. Minor releases such as 3.12.4 are reserved for bug fixes. The idea is to make each minor release more stable than the previous one, and allow customers to more easily upgrade to stable releases. There is more information about how our products are versioned here:
http://confluence.atlassian.com/display/DEV/Versioning+of+Releases

We have partners who specialise in customising and extending JIRA, as we do not do sponsored work ourselves. If you are interested in working with a partner please send an e-mail to:
partners at atlassian dot com

Another thing you may wish to look at is a greasemonkey script written by one the JIRA users:
http://confluence.atlassian.com/display/JIRAEXT/JIRA+Greasemonkey+Worklog+Helper
I have not personally used it, so I am not sure how well it work. If it does, it might really help.

Cheers,
Anton