WorklogListener - Modify the creation time for a worklog

Hello Jes,

I tried using the following inputformat (and the same as outputformat) values:

dd/MMM/yy hh:mm a

dd/MMM/yyyy hh:mm a

But they did not work. Instead the format dd.MM.yyyy HH:mmwas always accepted, independently of the formats specified in the configuration. I'm using as a test system Jira 3.5.1 enterprise standalone on Windows.

Cheers

Bettina Zucker 

Why is this page not linked from the extensions home?

Something is wrong.  I cannot download the attachmed jar.  Clicking on it gives me this error:

java.lang.RuntimeException: Attachment data not found where expected
 at
com.atlassian.confluence.pages.DefaultAttachmentManager.getAttachmentData(Lcom/atlassian/confluence/pages/Attachment;)Ljava/io/InputStream;(DefaultAttachmentManager.java:36)

                        caused
by: com.atlassian.confluence.pages.AttachmentDataNotFoundException:
Problem while getting attachment stream from file system
 at
com.atlassian.confluence.pages.persistence.dao.FileSystemAttachmentDataDao.getDataForAttachment(Lcom/atlassian/confluence/pages/Attachment;)Ljava/io/InputStream;(FileSystemAttachmentDataDao.java:84)

                        caused
by: java.io.FileNotFoundException:
/var/lib/pgsql/opt/j2ee/domains/atlassian.com/confluence/webapps/atlassian-confluence/data/attachments/162015/5596:
No such file or directory
 at jrockit.io.FileNativeIO.open0(Ljava/lang/String;I)I(Unknown Source) 

PS - It's cool that the system's favorite color is Chartreuse...

Hi Everyone,

It seems like some of the attachments were lost during an upgrade. We're currently looking into the problem, and hopefully all the files will be back up soon.

Thanks,
Brian

Sorry about that folks. The attachments have been restored.

HelloJes,

I have to upgrade to Jira 3.6.x so I tested this plugin with a test installation of Jira 3.6.1 enterprise.

The plugin did not work. I used the standard format_:  [Date: dd.MM.yyyy HH:mm]_
The string was left in the comment and the worklog's date is today.

I got some error messages:

2006-05-23 15:17:01,008 ERROR [velocity] RHS of #set statement is null. Context will not be modified. templates/plugins/portlets/issuesummaryfastworklog.vm [line 23, column 1]
2006-05-23 15:17:01,101 ERROR [velocity] ASTMethod.execute() : exception invoking method 'getPrettyDuration' in class com.atlassian.jira.issue.helper.WorklogHelper : java.lang.IllegalArgumentException: argument type mismatch
2006-05-23 15:17:01,148 ERROR [velocity] RHS of #set statement is null. Context will not be modified. templates/plugins/portlets/issuesummaryfastworklog.vm [line 26, column 1]
2006-05-23 15:17:59,351 ERROR [velocity] RHS of #set statement is null. Context will not be modified. templates/plugins/portlets/issuesummaryfastworklog.vm [line 23, column 1]
2006-05-23 15:17:59,351 ERROR [velocity] ASTMethod.execute() : exception invoking method 'getPrettyDuration' in class com.atlassian.jira.issue.helper.WorklogHelper : java.lang.IllegalArgumentException: java.lang.ClassCastException@d5a86c
2006-05-23 15:17:59,445 ERROR [velocity] RHS of #set statement is null. Context will not be modified. templates/plugins/portlets/issuesummaryfastworklog.vm [line 26, column 1]
 

At the moment I'm considering just not installing the plugin in 3.6.x, since worklogs were not accepted by our users yet.
They are still too complicate. So I'm not requesting you to correct the plugin, just wanted to tell you about my negative test result.

Cheers

Bettina Zucker 

The listener for 3.6.x seems to be broken : on the log work page, i put in 22m, and as comment i put in [Date: 01/02/2006]. When looking at the work log overview in the ticket i get:

Time Worked: 22 minutes [Created: 02/35/2006]    -> i don't think that's a legal date

The listener is configured as dd/mm/yyyy, using Jira Enterprise Edition, Version: 3.6.1-#154

Hi,

the workloglistener seems to not work with my jira 3.6.x installation anymore. The jar is in the WEB-INF/lib directory, I can add the listener to the listeners in the admin page and have specified
When I now add a worklog with this date format, the result looks like this:

Hence, no change to the date has been made. I tried [Date: 01.08.2006 20:00] and [Date: 1.8.2006 20:00]. Still no change. Any advise would be greatly appreciated. We are heavily using this feature for getting accurate worklogs.

Thanks!

- Peter 

Hi we installed this plugin recently and we have had a problems with it.

When entering time into the system the date we specified would be increased by 12 hours for an unknown reason.
For example, when entering [Date: 05/10/06 20:00] the worklog would be logged at 8:00 and the date would be increased by one. So it would be logged as 06/10/06 8:00

We got around this by specifying an input format at the edit listener page but I just wanted to bring it to your attention.
  

The above is in JIRA 3.6.4 build 160

The Date should be strictly validated, for example, someone can even fill their worklog years ago or later. That's unreasonable.

Hi Jes,

Can you confirm whether or not this plugin is working in version 3.7.1?  I've just upgraded and reinstalled this and it's not functioning as expected.  It's almost as if the listener is being ignored?

Cheers

Jes, does your worklog listener work with 3.7? Our company is looking at JIRA again but may not get it because of this weak time tracking issue.

Any progress with 3.7.3?

Hi Jes,

Is this working in Version 3.9?  Can't seem to get it going?

Cheers