Weekly Timesheet 1.1
Added by Dhanasingh Krishnapandian about 12 years ago
We are happy to announce the Weekly Time Sheet plugin version 1.1
Following are the features for 1.1
- The plugin is made compatible with Redmine 2.1.0
- Issues can be entered as Id
- Work time header can be configured to show/hide
- Allowing blank issues can be configured
Thanks to Bob Pack, Olivier Pinette, Karol Zaren for their feedback.
Dhanasingh
Replies (23)
RE: Weekly Timesheet 1.1 - Added by Bart van Kleef about 12 years ago
Thanks a lot for this amazing plugin!
We found one annoying bug. When multiple subprojects exists with the same name, issues of the last added subproject are shown under other subprojects with the same name. I'll explain with an example project structure:# Project, subproject, issues Customer 1 Support # 1. (red in attached images) Customer 1 A Customer 1 B Customer 2 Support # 2. (orange in attached images) Customer 2 A Customer 2 B Customer 3 Support # 3. (yellow in attached images) Customer 3 A Customer 3 B
What you will see in the attached images is that:
- Issues existing (Customer 1 A and Customer 1 B) in project Customer 1, Support are not displayed, instead of that the issues of project Customer 3, Support are shown;
- Issues existing (Customer 2 A and Customer 2 B) in project Customer 2, Support are not displayed, instead of that the issues of project Customer 3, Support are shown;
- Issues existing (Customer 3 A and Customer 3 B) in project Customer 3, Support are displayed fine.
Is there anyway to solve this without renaming the (sub)project names?
Kind regards,
Bart van Kleef
RE: Weekly Timesheet 1.1 - Added by Dhanasingh Krishnapandian about 12 years ago
Bart,
thanks for reporting the problem.
Just for testing purposes, could you rename the sub projects to Support 1, Support 2 and Support 3 and see if you are getting the issues right. I have a feeling you are probably not choosing the right sub project.
Anyways, we will take a look and get back to you.
Dhanasingh
RE: Weekly Timesheet 1.1 - Added by Bart van Kleef about 12 years ago
Dhanasingh,
Thanks for your reply.
I've attached some more images:- As you can see, reporting time by the default Report time option in Redmine displays project ID's for all projects that are not lastly added (with the same name);
- After renaming the subproject names everything works fine.
Let me know if you need any other information.
Kind regards,
Bart van Kleef
RE: Weekly Timesheet 1.1 - Added by Dhanasingh Krishnapandian about 12 years ago
Bart,
We are able to reproduce this problem in our test environment and acknowledge that this a bug.
we will fix it in the next release.
thanks
Dhanasingh
RE: Weekly Timesheet 1.1 - Added by Bart van Kleef about 12 years ago
Dhanasingh,
Thanks a lot for your research into this. We are looking forward to the next release! Can you give an indication of this release date?
Again, thanks a lot,
Bart van Kleef
RE: Weekly Timesheet 1.1 - Added by Dhanasingh Krishnapandian about 12 years ago
In a couple weeks, we should have 1.2 out.
The major features of 1,2 are
- Approval System (Submit, Approve, Reject, Unsubmit)
- Custom fields for Weekly Timesheet
RE: Weekly Timesheet 1.1 - Added by Bart van Kleef about 12 years ago
Dhanasingh,
Sounds amazing, keep up the great work!
Kind regards,
Bart van Kleef
RE: Weekly Timesheet 1.1 - Added by Michael Zhu about 12 years ago
feature request:
support to report weekly time of all projects user participated.
Dhanasingh Krishnapandian wrote:
In a couple weeks, we should have 1.2 out.
The major features of 1,2 are
- Approval System (Submit, Approve, Reject, Unsubmit)
- Custom fields for Weekly Timesheet
RE: Weekly Timesheet 1.1 - Added by Dhanasingh Krishnapandian about 12 years ago
Michael,
This feature is already available.
A user can submit time to all the projects he is a member of.
Dhanasingh
RE: Weekly Timesheet 1.1 - Added by Michael Zhu about 12 years ago
Dear Dhanasingh,
I want to Weekly Timesheet help generate weekly report of one user.
One filed is used to choose user, another filed is used to choose project. But now,
only one project can be chosen once time. I hope all projects the user participated
can be chosen. For example, use '-' to represent all projects the user participated.
My English is not good. Sorry!
Dhanasingh Krishnapandian wrote:
Michael,
This feature is already available.
A user can submit time to all the projects he is a member of.Dhanasingh
RE: Weekly Timesheet 1.1 - Added by Dhanasingh Krishnapandian about 12 years ago
Michael,
which page are you talking about ?
if you are talking about the new page (http://server/wktime/new).
The project drop down is only used to filter the following user drop down.
Once you choose a project, it will populate the user dropdown with that project members.
The project drop down is of no signifance here, because it only allows you to narrow down on the user.
thanks
Dhanasingh
RE: Weekly Timesheet 1.1 - Added by Michael Zhu about 12 years ago
Dhanasigngh,
The feature I mentioned is already available. sorry.
New Timesheet --> select one member, one project --> continue
Weekly Time sheet of user is reported. The users jonined mulitple projects, and weekly time sheet
can report. And then I ask to export PDF.In PDF file, in the table, list project name under Project
column, but before the table, there is a field named Project, but it list only one project name.
RE: Weekly Timesheet 1.1 - Added by Dhanasingh Krishnapandian about 12 years ago
Michael,
Glad to know you are able to be find the feature you are looking for.
And regarding the project name in the PDF, yes, it shows only one project in the header.
How do you want that handled, do you want all project names with comma separated ?
Dhanasingh
RE: Weekly Timesheet 1.1 - Added by Michael Zhu about 12 years ago
I think it's not necessary to have the field, because project name exists in the table.
B.T.W. would you like to add hyper link to issue id in PDF file ? If added, boss can jump
to the issue easily.
Dhanasingh Krishnapandian wrote:
Michael,
Glad to know you are able to be find the feature you are looking for.And regarding the project name in the PDF, yes, it shows only one project in the header.
How do you want that handled, do you want all project names with comma separated ?Dhanasingh
RE: Weekly Timesheet 1.1 - Added by Dhanasingh Krishnapandian about 12 years ago
ok, lets hear from others if they are ok with deleting the project field from the header of the pdf export.
I will add the hyperlink issue to our feature list for the next release.
RE: Weekly Timesheet 1.1 - Added by emma dcosta about 12 years ago
Hi Dhanasingh,
thanks for sharing the information. In fact we had been using another cloud based Timesheet Software (http://www.replicon.com) by Replicon. Its simple to use and quick to implement.
RE: Weekly Timesheet 1.1 - Added by Olivier Pinette about 12 years ago
Hi Dhanasingh,
Here an other question (may be a feature request) I would like to share...
When I create or modify a Timesheet, I first select a project, then the issue... but the issue list-box include issues from all trackers.
The problem I have is I would like to track time only for some of these trackers
Example: please consider 2 trackers: Tasks, Milestones. In this case I would like to report time on tasks only, but unfortunately the issue list box provide all tasks + all milestones.
Does any one also failed into this problem?
Any solution, workaround ... to this issue?
If not, does it make sense to consider this as a feature request for a future version?
Thank you again for your lovely and valuable plugin and all your effort to maintain and enhance it.
Olivier.
RE: Weekly Timesheet 1.1 - Added by Dhanasingh Krishnapandian about 12 years ago
Olivier,
Are you thinking of a dropdown for tracker next to Project dropdown ?
Wouldn't this additional dropdown make data entry little more difficult?
And by the way there is another request from Sylvain Hamel on making the issue field
as text box, allowing for free text and providing a list of matches like the 'Parent Task'
field on the Issue Page. What if we implement that feature, would that work for you ?
Dhanasingh
RE: Weekly Timesheet 1.1 - Added by Olivier Pinette about 12 years ago
Thank you for your answer Dhanasingh,
Let me try to clarify and/or think-aloud...
The possibility to enable/disable Time tracking exist at project level and I my need is to be able to enable/disable Time tracking per trackers too.
I'm asking to myself if it doesn't make more sense to consider this request as a feature request for the Redmine core product, since the impact is larger than the Weekly Time page. Indeed the "edit issue" page is impacted too for example.
Now let me answer to your proposal...
Dhanasingh Krishnapandian wrote:
Are you thinking of a dropdown for tracker next to Project dropdown ?
Wouldn't this additional dropdown make data entry little more difficult?And by the way there is another request from Sylvain Hamel on making the issue field
as text box, allowing for free text and providing a list of matches like the 'Parent Task'
field on the Issue Page. What if we implement that feature, would that work for you ?
- The request from Sylvain cannot solved my issue, because on the issue list we haven't a clue of the associated tracker.
But this gave me an idea: It could be nice to provide the Tracker in addition to the Id and Subject in the issue drop-box (eg: Today it looks like "44 - My issue", what about using same format as on the roadmap : Defect#44: my issue".
This not solved my problem, but will provide clue to the user regarding the associated tracker... and it is probably easy to do.
- regarding your idea to have an additional drop-box next to the project drop-box, I'm totally agree with you data entry must be as simple and quick as possible.
- Add a filter to populate the issues drop-box with desired trackers only (may be with a set of check-box at the top right of the entry data page allowing to select trackers to consider)
- The filter capability could also be included in the Weekly Time-sheet Plugin settings page
- Using this way, in the plugin configuration page the administrator could set default trackers to consider, and user will be able to alter default filter according his need in the entry data page.
Let me know what you think about...
Thank you again for your help.
Olivier.
RE: Weekly Timesheet 1.1 - Added by Dhanasingh Krishnapandian about 12 years ago
Olivier,
We will take both these requests into our feature list
1) add tracker to the issue name and id
2) enabling issue filtering by tracker.
Dhanasingh
RE: Weekly Timesheet 1.1 - Added by Olivier Pinette almost 12 years ago
Dhanasingh Krishnapandian wrote:
Olivier,
We will take both these requests into our feature list
1) add tracker to the issue name and id
2) enabling issue filtering by tracker.Dhanasingh
Dhanasingh,
First, thank you again having implement #1 in WT 1.3.I receive a new interesting request from one of my user, I would like to add in my wish list for your plugin.
- First, let me start with description of the initial need : When user start a new time-sheet, the "Previous Week's as template" option help but to simplify his life a little more, it could be interesting to also join the maximum list of recurrent issues to this template. When I say "recurrent" it means issues what will not be used every weeks but frequently.
- To address this need I have 2 ideas
- Allow users to register a list of recurrent issues to consider as part of the time-sheet template (This require to manage one list of recurrent issue per user) this is the heavy solution.
- transform the "Previous Week's as template" option to consider more than one weeks. This is the light solution. The number of week to consider could be a new plugin settings. Then, when user engaged the "Previous Weeks's as template" option, he will receive the list of distinct and non closed issues from the number of previous weeks as template.
Have you identify this user needs? What do you think about solutions/ideas?...
Regards.
Olivier.
RE: Weekly Timesheet 1.1 - Added by Dhanasingh Krishnapandian almost 12 years ago
No, We have not had this request before, we will consider it as a feature request.
Yeah, option 1 will be more involved and require us to persist the template and its issues in the database
Option 2 is easier, we will go with that for now and come back to option 1 at a very later time :-)
Dhanasingh
RE: Weekly Timesheet 1.1 - Added by Olivier Pinette almost 12 years ago
Sounds perfect. Thank you Dhanasingh :-)