|
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Simone Avanzi - 23/Jul/03 12:16 PM
I really think this could be VERY useful. Please take a look at the issue linked also which is similar.
also consider the issue JRA-11336 when solving this
Hello,
This issue has been open for four years - is there a resolution planed? Kind Regards, This is really becoming a major issue in correctly tracking time on projects. Adding the ability to make it mandatory is something I could really use.
Sad that it four years and still isn't in JIRA This would be an extraordinariy useful feature - integrating work done into the workflow. Workflow (obviously) is enforced, and if there was some way to ensure that entering "work done" when an issue was resolved/closed was enforced, it would radically improve the accuracy, and therfore usefulness of the work done field.
As it is, there is an awkwad requirement to do the following when you are finishing off an issue: This double closing is both awkward and clumsy. Ideally, we could move the "Log Work" fields into the Workflow Screens, so the workflow would look more like the following: o Click on "Close Issue" Much more streamlined, and increases the quality of the capture time spent data by enforcing some form of workflow. I'm using 3.10 version, and I also need to log Time spent when solving or closing an issue.
This is what I've found :
http://jira.atlassian.com/browse/JRA-868?focusedCommentId=89610#action_89610 
It's a plugin called JIRA Suite Utilities. But the Time spent field does not appear in the transition screen. It would be better to add the Time spent field in a transition screen (which is possible for other fields), Regards, Julien. Just to put my oar in here: we could use this functionality too. It's tricky to coerce our developers into logging their times, but if it was keyed to them being able to mark an issue as "resolved" they'd start toeing the line nicely.
Thanks julien ,
My problem is am not to see the Original estimate & Time spent at the time of adding validation for a workflow transition. Problem : we defined the customized workflow, there it has StartProgress and Fixed transitions. so that i can calculate the time. o.w can i make the logwork done mandatory at the time of Fixed Transition Pls help me on this So we pay ungodly amounts of money for this product, no one is in disagreement that this is a valid and necessary request, and 4 years later not a single Atlassian employee has even responded to it. Wonderful.
As we wait for Atlassian to acknowledge this request, has anyone found a work around?
Without sounding too cynical, the best workaround is to use a different product. We've been using JIRA for nearly a year now and for the most part it has been good for our team. As our team gains experience and wants to do more advanced things like time tracking, we've run into a brick wall in terms of Atlassian's response to this issue. The issue has been open for NEARLY 5 YEARS and yet there has been no move by Atlassian to resolve the issue, or even offer a quality workaround.
I'm the person in our organization that chose JIRA and I'm the one taking flak for this limitation. It is very possible that we will not be using JIRA in the future and this issue is a big factor in that decision. I think the expectation is that engineers don't do time management in their bug tracking, and people who require time management for their tasks use a different system (Remedy, Project Insight come to mind).
It's definitely true that Jira, out of the box, doesn't provide much in the way of managing time utilized in projects. The recent upgrades to allow back-dating entry of time worked, has been useful, but the inability to ensure time is entered on a task before it is closed results in about 20-25% data entry on our IT based jira tasks - and that's only after a reasonable amount of follow up on my side. If I'm not mistaken - Jira still doesn't even allow you to enter how much time, and when, you've worked on a Jira Task when closing it - let alone ensure that you've entered the data when closing it. I have to guess this is relatively easy to do - so I'm hoping that eventually enough people will vote on this issue and it will float up to the top of the pile. Atlassian will follow their customers, so I'm guessing time tracking really isn't that important to their customers right now. Until then, just realize - Jira is not a project management tool - it's a outstanding task tracking/bug tracking tool, and you should be fine. Well, you can do a lot with plugins, but this means custom developement and usually scrapping all existing functionality. It's not as infeasible as it sounds, as time-tracking requirements differ wildly between companies anyway. We've implemented our own timetracking plugin with a lot of very specific functionality (hierarchic linking, bulk entry, custom export for reporting...) in about a month.
If you don't want do it yourself, take a look at http://confluence.atlassian.com/display/JIRAEXT/Kaamelot |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Open
Major
"Log work done" as a MANDATORY field when resolving issues
