|
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Anton Mazkovoi [Atlassian] - 09/Nov/03 11:31 PM
Maybe add another permission, to allow certain users to edit work log.
Looking at the number of time this issue has been raised, it seems important for a relatively high number of people.
Are you looking into scheduling this issue for a near release. I think this and the ability to log work for a date/time in the past are vital.
It seems that the priority of this issue should be raised, based on the amount of duplicate issues. Some of the duplicate issues are marked as critical.
I can not have my engineers fill in the worklog if the worklog can not be modified - in case of a faulty entry. I can therefore not produce accurate / reliable statistics to my manager and ISO auditors. +1 on additional feature request by Mark Johnson.
What is the exact status of that issue ?
It causes us a lot of trouble in maintaining correctly the worklog ? Is there any way we can prioritize that issue ? As long as we are concerned in our enterprise, this is considered as a BUG and not an IMPROVMENT !! I hope somebody will look at that fast and find a solution. Thanks. You can create worklogs with minus minutes.
e.g. -120 will subtract 2 hours from the time worked. Work log should be definitely improved by adding the ability to delete a worklog.
If I entered a negative number, the work log tab of the issue is buggy since it doesn't display anything for negative work logs... I think it's quite a big bug that do not confort the user in using this feature... Yes Anton, an edit work log permission should be interesting. This feature should allow to delete or modify work logs.
But you should then add a new role : "work logger". In fact, the current assignee should be different from the one that entered a previous work log and it should be difficult without this role to define a dynamic permission... So, a "work logger" role could contain the list of people that putted a work log in the current issue. +1 regarding the feature to log work in the past also... There is now a workaround (editworklog.jsp) for this problem described at:
owen brand commented on
--------------------------------- Is there some way that the USER can use this workaround? It's not much The proposed workaroud is not practical, the administrator could already go into the database and delete it directly.
Users must be able to delete a worklog entry. A new privilege should be introduced to limit the use of this funtion to specific groups/roled/individuals. This is an updated version of the jsp that will work against the Jira 3.2.x codebase.
Adding the latest version of the patch. Works with 3.3 and above.
Some feedback on workaround.
If issue didn't have any estimates and user enters wrong time, say 2h instead of 1h, and when I use the tool to change the worklog back to 1h, the remaining estimate field value increases by the difference between the "wrong" time and new "correct" time. this would be an excelent addition to this product
I have to add to this as well that editing a previous work log is necessary especially to the user who mis-entered the information.
Also, it is necessary to associate a work log with a certain date/time of day. Is this possible? Thanks, Peter Hi,
In regards to entering a date the work should be logged against, please vote for: Cheers, When an issue has many work logs the JSP tends to slow down disproportionately. Attached is a faster version of the script.
If one has many work logs it also would be better to place the form over the table. Adding new related tasks:
We're switching to Scrum and are banging our heads to the wall trying to use Jira for the issue tracking with the work logs. The current time tracking in Jira is nice but missing the few critical features that'd make it actually usable in an every day working environment. Hi,
To resolve the problem with not being able to register a worklog with a date/time in the past I have developed a simple Listener. Hi Jes,
If you would like to share your listener, it would be cool if you could upload it to our extensions space  . There are instructions on the page about how to upload. Thanks for this.Dylan See WorklogListener - Modify the creation time for a worklog
for a simple Worklog Listener which make it possible to change the "Creation" date for a worklog. It'd be great if this little listener stored an audit log of modifications somewhere. I don't really like the idea of people just modifying creationdate with wild abandon.
Do you have any ideas about how this might be done? Actually, strike my previous comment. After reading the confluence page, I see that you've already done this with the comment.
I wonder if there is a small copy&paste issue with this sentence... Result: Should read: Result: Hi Denis,
Your right about the copy&paste... It's corrected now. About logging: Your quite right, it should be done probably. The Listener is of course a hack, and from this issue I can se that Atlassian will take care of a more user friendly way to administer work logs. So for the time being I'll hold further features. This is very core functionality to task tracking, and nearly every user will hit it at one time or another. It's very difficult to get a team to adopt Jira and benefit from all of the innovative features and power when basic features like this are a barrier to entry with our management. Please seriously consider this issue in the near future.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Improvement
Resolved
Critical
Ability to edit and remove work logs
