Description of problem: Please clarify the reason behind this. I believe the ideal solution would be to default all date boxes to today's date - the additional radio box is confusing. If this is the only solution at present, currently the box is not checked by default and the date is not displaying in the date field Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.create an event 2.View date fields 3. Actual results: Expected results: Additional info:
Pre-filling all the text boxes with the current date would complicate matters for date fields which are typically optional, since the user now has to manually remove all the pre-filled data.
What if we make it easier for the user to select the current day (if they so desire) by populating the drop-down list in the following order: today (16th) 1 2 .. 15 16 17 .. 31
Current the "day" field is a text field, not a drop down so that is not possible with the current widget and would require converting to a text box (probably with javascript to change depending on the selected month). The check box defaults to true for most dates. However, it defaults to unchecked for things like "launch date" where the user would rarely want to use "today". It also is "unchecked" if the date already has a value so that the current value is not overridden. However, in most cases if the item does not have a current value it should default to being checked.
It just looks very messy with the day field blank and a 'today' box next to the field - Can I ask you to suggest a solution the best option considering present timescales
In addition, the requirements as stated (at least as I received them) included the 'today' toggle. For this week, there's nothing new we can do. As for changes before final release, to make any change would require a change which doesn't impact current functionality. For optional fields, automatically filling in today's date would cause fields which ought to remain blank to be accidentally filled in.
I have had a detailed look at this again today. My recommendations are: 'today' toggle does not check today's date as it stands so is not working correctly. At present, the current date widget is inconsistent. Controlled lists for month and year are present but day is just a text box. This really needs to be improved so that the way each field works is consistent. There is no problem about the day list containing 1-31 and a user resolving how many days in the month. By default all lists could contain a blank so that the user chooses month day and year or leaves blank if required. The today toggle would not necessarily be needed unless if you checked it, it would automatically fill the boxes with todays date. In some cases today's date is filled automatically e.g. lifecycle start date - I assume you could still do this. Please let me know how we can resolve this
As discussed during our meeting last week, we will remove the 'today' checkbox altogether since it just doesn't work well in practice. The longer term solution will be to incorporate a JavaScript popup date picker. We'll evaluate how much work this will involve to determine when we'll be able to integrate such functionality.
Dan, does this mean we should simply revert Randy's changes entirely, going back to prior behavior?
Remove the 'today' checkbox altogether, putting Date field back to what it originally was prior to WS3
Removed @40477.
I'm still seeing the today checkbox.
QA_READY has been deprecated in favor of ON_QA. Please use ON_QA in the future. Moving to ON_QA.