Feature #2269
closedDefault issue start date should become configurable.
0%
Description
Currently, the start date field of new issue is fixed as today.
(in issues_controller.rb, def new, )
My company has a rule project manager or assignee must input a start date and due date when (s)he start a patch or implementation task. Current default function of new issue creation make my fellows confuse.
Also in gantt or calendar, the start date of newly created issues is displayed as default.
But a planning person, project manager want to define a term of each task.
So, I want for administrator to set the value of 'using today as start date on creating issue'.
In simple development org., this feature is not required.
But more tighten development org. might want this feature.
Files
Related issues
Updated by samir djouadi almost 16 years ago
- Status changed from New to Resolved
- Assignee set to Liwiusz Ociepa
Updated by Jean-Philippe Lang almost 16 years ago
So, I want for administrator to set the value of 'using today as start date on creating issue'.
How could you set a value for this option? It seems more like a yes/no option.
If set to 'no', no date would be set by default when creating an issue.
Updated by Jean-Philippe Lang almost 16 years ago
- Status changed from Resolved to New
Updated by Mischa The Evil almost 16 years ago
Jean-Philippe Lang wrote:
So, I want for administrator to set the value of 'using today as start date on creating issue'.
How could you set a value for this option? It seems more like a yes/no option.
If set to 'no', no date would be set by default when creating an issue.
I've created and uploaded a simple patch (#2277) which adds such a yes/no-option and related the issue to this one.
Please let me know if an implementation like this is, is the way to go or not... :-)
Updated by Kihyun Yun almost 16 years ago
Mischa The Evil wrote:
Jean-Philippe Lang wrote:
So, I want for administrator to set the value of 'using today as start date on creating issue'.
How could you set a value for this option? It seems more like a yes/no option.
If set to 'no', no date would be set by default when creating an issue.I've created and uploaded a simple patch (#2277) which adds such a yes/no-option and related the issue to this one.
Please let me know if an implementation like this is, is the way to go or not... :-)
Yes, I think that a value for this options is a boolean value.
Thanks.
Updated by Bruno Medeiros about 14 years ago
- Assignee deleted (
Liwiusz Ociepa) - % Done changed from 100 to 0
Why change %done to 100 if it's not done?
Even filling blank in the start date doesn't work anymore, please fix it. The start date should not be the creation date by default, the gantt chart is completely wrong that way.
Updated by Beau Simensen over 13 years ago
Updated by Mischa The Evil about 13 years ago
- Subject changed from Issue start date's default value can be selectable. to Default start date value should become configurable.
- Category changed from Issues to Issues planning
- Target version set to Unplanned backlogs
I've modified the subject and category according to the actual subject and the related issues to be better recognizable.
I've targetted it to the 'Unplanned' version since it's definitely a feature a lot of users (including myself, so I'm a bit biased) want to get in.
I'd suggest to discuss the implementation of this further on issue #2277 to keep it clear (plus the TODO's I've mentioned on issue #2277note-10 are still present AFAIK).
Updated by Mischa The Evil about 13 years ago
- Subject changed from Default start date value should become configurable. to Default issue start date should become configurable.
Updated by Etienne Massip almost 13 years ago
- Status changed from New to Resolved
- Target version changed from Unplanned backlogs to 1.3.0
- Resolution set to Fixed
Fixed with r7733.
Default setting is to set start date to issue's creation date for backward compatibility.
Updated by Mischa The Evil almost 13 years ago
Thanks for committing this Etienne. Glad to see this finally made it into the core tested and well.
Updated by Mischa The Evil almost 13 years ago
I've just had a second look at the implementation and noticed two things I'd like to discuss before finally closing this issue:
- the used English i18n is plain wrong; both grammatical as well as in style:
As far as I was able to find out (English is not my native language):Set new issue's start date with today's date value
should beSet new issues start date with todays date value
to be correct English (see e.g. http://www.cgl.uwaterloo.ca/~csk/its.html). This new string does not look like it is nicely styled English to me.
Considering the above I suggest we use a new i18n-string (inspired by the implementation in ChiliProject).
That would replace the currently used i18n-string:Set new issue's start date with today's date value
with:Use current date as start date for new issues
I'll attach a patch for this change which changes the English strings and re-inserts the new string for the already translation languages (fr and bg).
- this one is regarding the chosen name for the new setting; it might be confusing for some users:
Now it looks like the issue creation date is set to the default issue start date, which is wrong. (To keep the Hungarian notation in tact :) I propose to change it from:default_issue_start_date_to_creation_date
todefault_issue_start_date_is_creation_date
orcreation_date_is_default_issue_start_date
I can attach a patch for this also, but would like some feedback first before making decisions upfront.
Updated by Etienne Massip almost 13 years ago
Mischa The Evil wrote:
the used English i18n is plain wrong; both grammatical as well as in style:
I can conceive that easily, I was not very sure of the correctness of my translation
(BTW, today's date is correct) :p
Use current date as start date for new issues
seems fine to me; no need to make a patch, though, this is a quick F&R fix.
this one is regarding the chosen name for the new setting; it might be confusing for some users:
I actually don't use any Hungarian notation here, ??Default X to Y?? is used as a verb in its infinitive form.
The actual name seems fine to me, could some native English speaker tell us?
Updated by Bruno Medeiros almost 13 years ago
I've already translated it to pt_BR, and didn't see it on r7733. Could you please integrate?
setting_issue_startdate_is_adddate: Usar data corrente como data inicial para novas tarefas
PS.: Use default_issue_start_date_to_creation_date
seems ok to me as default is acting as a verb.
Updated by Mischa The Evil almost 13 years ago
Etienne Massip wrote:
Mischa The Evil wrote:
the used English i18n is plain wrong; both grammatical as well as in style:
I can conceive that easily, I was not very sure of the correctness of my translation
(BTW, today's date is correct) :p
Woot... :-S This is sometimes rather difficult for me as a non-native speaker of the English language. I've even heard that native English speakers sometimes have difficulties doing this grammatically right...
Etienne Massip wrote:
Use current date as start date for new issues
seems fine to me; no need to make a patch, though, this is a quick F&R fix.
Thanks for already committing this change into trunk.
Etienne Massip wrote:
Mischa The Evil wrote:
this one is regarding the chosen name for the new setting; it might be confusing for some users:
I actually don't use any Hungarian notation here, ??Default X to Y?? is used as a verb in its infinitive form.
The actual name seems fine to me
Forget about my nitpicking, figurative speech and, personal language barriers here ;) It's fine for me as it is now. I think most others will agree here too, so consider this done.
Again, thanks for your efforts on this issue...
Updated by Jean-Philippe Lang almost 13 years ago
- Status changed from Resolved to Closed
Updated by Etienne Massip almost 13 years ago
Bruno Medeiros wrote:
I've already translated it to pt_BR, and didn't see it on r7733. Could you please integrate?
[...]PS.: Use
default_issue_start_date_to_creation_date
seems ok to me as default is acting as a verb.
I didn't because the English string was changed so I thought that the translation was no more accurate.
Updated by Pierre Pretorius almost 13 years ago
We run a large amount of development projects on Redmine and use this feature. Thanks for implementing.
Updated by Bruno Medeiros almost 13 years ago
Etienne Massip wrote:
Bruno Medeiros wrote:
I've already translated it to pt_BR, and didn't see it on r7733. Could you please integrate?
I didn't because the English string was changed so I thought that the translation was no more accurate.
Ok, makes sense. :)
Thanks for integrating anyway!
Updated by Luis Serrano Aranda over 12 years ago
I think the better option is configure this option in every project