Project

General

Profile

Weekly Timesheet 1.3

Added by Dhanasingh Krishnapandian about 11 years ago

We are happy to announce the release of Weekly Timesheet 1.3
Here are the features included in 1.3, our primary goal is to
make it compatible with Redmine 2.2

- Plugin is made compatible with Redmine 2.2.0
- Added Unapprove button to unapprove a approved timesheet
- Appended tracker with issue in issue dropdown
- Removed project name from pdf header

Dhanasingh


Replies (56)

RE: Weekly Timesheet 1.3 - Added by Jean-Michel Biollaz about 11 years ago

I have installed the Weekly timesheet 1.3 plugin on a Redmine 2.2.1, when I click on New timesheet in weekly time the member list is always empty, no matter of the project selection, and when I click on 'Continue' I get a 403 You are not authorized to access this page.
Note that in the main weekly time page (i.e redmine/wktime/index) I can select the project and see the members.
My login is an administrative one and I'm manager of the selected project, do you have any idea of what is missing?

The add row link also has no effect
(Browser Chrome Version 24.0.1312.52 m)

Thank you,
Jean-Michel

RE: Weekly Timesheet 1.3 - Added by Dhanasingh Krishnapandian about 11 years ago

Jean-Michel,
that is strange, both index and the new page uses the same javascript and ajax.
Can you check if the ajax is getting called when you change the project,
you should see a small "loading" icon flashing when the ajax is called.

or do you see any javascript errors ?

What version of plugin, browser, browser version are you running ?

Dhanasingh

RE: Weekly Timesheet 1.3 - Added by Jean-Michel Biollaz about 11 years ago

Dhanasingh,

I didn't see any loading icon flashing.

However after displaying the javascript error console under Chrome I have noticed the following error:

GET redmine/plugin_assets/redmine_wktime/javascripts/index.js 404 (Not Found) index:28
Uncaught ReferenceError: projChanged is not defined index:86

After verifying, the js resources files appear to be missing in the asset plugin directory.
By redeploying the plugin everything is now working fine.

Thank you for your support,
Jean-Michel

RE: Weekly Timesheet 1.3 - Added by Dhanasingh Krishnapandian about 11 years ago

Glad to know it is working fine.
yeah, the assets folder from plugin will get copied over to public/plugin_assets folder when you start redmine.

Dhanasingh

RE: Weekly Timesheet 1.3 - Added by lijo jose about 11 years ago

Hi,

A gr8 app.Appreciate..

I have a req which is as follow

In Time sheet I have created an custom field "activity" drop down(List Box),now I need to create another custom field which will be a "SubActivity" dropdown ,i.e for example lets say I selected meetings from "Activities" drop down and in subActivities It should list only the subActivities for meeting which would configured like con-call,client meetings,stand up meetings..etc

Can you help me on this or suggest a workaround?

Regards

Lijo Jose

RE: Weekly Timesheet 1.3 - Added by lijo jose about 11 years ago

Dhanasingh Krishnapandian wrote:

ok, lets see if anybody else has got any comments on this item and take it from there.
thanks for the discussion.

Hi,

As you have mentioned in your response,a user with "Manage members" has the right to approve,reject the time sheet.Now the real problem for me is that different Groups(development team,testing team,project team managers )can see all the employee time-sheet irrespective of dept's?Is there a way we can restrict this in the time sheet withing dept's.

Any suggestions

Regards
Lijo Jose

RE: Weekly Timesheet 1.3 - Added by Dhanasingh Krishnapandian about 11 years ago

Lijo,
The nested / related custom fields are going to be tough to impleent, I don't think even redmine doesn't support this.

Dhanasingh

RE: Weekly Timesheet 1.3 - Added by Dhanasingh Krishnapandian about 11 years ago

Lijo,
If a member is assigned to only one project, then only that project manager can approve his timesheet.
If he is assigned to two projects, then both the project managers can approve his timesheet.

So please check their project assignments.

Dhanasingh

RE: Weekly Timesheet 1.3 - Added by lijo jose about 11 years ago

Dhanasingh Krishnapandian wrote:

Lijo,
If a member is assigned to only one project, then only that project manager can approve his timesheet.
If he is assigned to two projects, then both the project managers can approve his timesheet.

So please check their project assignments.

Dhanasingh

Hi,
Thank you.Also by looking at the time tracker,it is based on a tracker and the issues under the selected tracker.

Now if the member has spend some time on documentation(nothing to do with the issues) how can the member enter this activity in the time tracker?

Regards

Lijo Jose

RE: Weekly Timesheet 1.3 - Added by Dhanasingh Krishnapandian about 11 years ago

Lijo,
Currently it is not based on a tracker, it is based on Project/Issue/Activity.
But in version 1.4 of Weekly Timesheet plugin, we plan to filter issues by tracker.

My recommendation on the documentation would be to just create an issue called 'Documentation' and log hours to it.

Dhanasingh

RE: Weekly Timesheet 1.3 - Added by lijo jose about 11 years ago

Hi,

The challange for me is that a project member might not only work on the project activities only, they might do some external activities like "Technical Reading","Training",'seminars" (items part of his/her kra) and it would help if we can have some provision to accommodate these entries in the time tracker.

Any suggestions?

Regards

Lijo Jose

RE: Weekly Timesheet 1.3 - Added by Dhanasingh Krishnapandian about 11 years ago

Not sure if this would work for you, but you can create a project called "Miscellaneous" and have these ("Technical Reading","Training",'seminars") as issues within that project. In our company we have a project called "Non Billable Work" to take care of tasks like these.

Dhanasingh

RE: Weekly Timesheet 1.3 - Added by Olivier Pinette about 11 years ago

Hello all,

I don't know if this could help, but as Dhanasingh, we are using the same way in our organisation. We have some Redmine projects designed only for time-tracking and/or internal task.

Olivier.

RE: Weekly Timesheet 1.3 - Added by Cristian Cabrera about 11 years ago

Hi Dhanasigh

I've been working with weekly timesheet, and works perfectly with the projects entered.

I have one big problem, I need to have a minimum of hours per day. In my case is 9 hours per day. I Try modifying your plugin, but I can not get it.

Can you guide me on how to implement it? I thought it would be good not to let me save the timesheet if I did not enter at least 9 hours and to give a warning message: "Unable to save timesheet: minimum hours per day: 9"

It is probable that you already have implemented.

Thanks

Cristian.

RE: Weekly Timesheet 1.3 - Added by lijo jose about 11 years ago

Hi,

Is there a way we can map the "Log time" entry in the issue tracker with the Weekly TimeSheet plugin to avoid redundant updates?

Regards

Lijo Jose

RE: Weekly Timesheet 1.3 - Added by Dhanasingh Krishnapandian about 11 years ago

Cristian,
This feature will probably be implemented in version 1.5

I think you can implement it in the javascript itself.
just bind a onclick method on the submit button.

and then call this method which is already there
calculateTotal(day)

if any of the day total is < 9, throw an error message and not submit the form.

Dhanasingh

RE: Weekly Timesheet 1.3 - Added by Dhanasingh Krishnapandian about 11 years ago

Lijo,
it is already there, when you enter time through the log time entry screen, it will automatically show up on hte timesheet.

Dhanasingh

RE: Weekly Timesheet 1.3 - Added by lijo jose about 11 years ago

Hi dhanasingh,

I wanted to add more than 2 custom fileds in your weekly plugin as we have start date,planned closure date,activity achieved,Actual closure?Can you pls suggest /
Regards

Lijo Jose

RE: Weekly Timesheet 1.3 - Added by Dhanasingh Krishnapandian about 11 years ago

Lijo,
Right now we are only allowing 2 custom fields in the row, but the rest of the custom fields will be available from the detail pop up, If you click on the icon next to the hours text box, the detail pop up should open up.

Dhanasingh

RE: Weekly Timesheet 1.3 - Added by lijo jose about 11 years ago

Dhanasingh Krishnapandian wrote:

Lijo,
Right now we are only allowing 2 custom fields in the row, but the rest of the custom fields will be available from the detail pop up, If you click on the icon next to the hours text box, the detail pop up should open up.

Dhanasingh

Hi,

Can we look at adding additional custom fields?Can it be done from our end?Also I have added a feild as date data type and mapped it to the custom fields in time tracker,but the column doesn't appear as date column in the time sheet?Any suggestion

RE: Weekly Timesheet 1.3 - Added by lijo jose about 11 years ago

Hi,

Also can you let me know the settings for removing the start and end from the weekly time sheet.Attached the screen shot for your ref(refer the red coloured area).

RE: Weekly Timesheet 1.3 - Added by Dhanasingh Krishnapandian about 11 years ago

Lijo,
if there are more requests from other people, we can take this as a feature request.
You will have to modify code if you need to achieve this from your end.

Thanks for pointing out the problem with custom date fields, we will take a look.

Dhanasingh

RE: Weekly Timesheet 1.3 - Added by Dhanasingh Krishnapandian about 11 years ago

To remove the start and end time from the weekly view, just uncheck the "Show Work time header" in the configuration.

RE: Weekly Timesheet 1.3 - Added by Cristian Cabrera about 11 years ago

Hi Dhanasingh

any posibility to include minimum hours per day in the next release?

I have been working in that feature, but i cant get it.

Cristian

RE: Weekly Timesheet 1.3 - Added by Dhanasingh Krishnapandian about 11 years ago

Cristian,
yeah, I know you were implementing the minimum hour feature.
you also said you have implemented the lock-by-friday feature too.

Anyways, We will most likely release 1.4 by end of this week, we are currently testing it.
I don't think we can implement this for 1.4.

We will put this in 1.5, which should be released next month.

Dhanasingh

(26-50/56)