taskSavane - Tasks: task #1039, field transition: other field...

 
 
Show feedback again

You are not allowed to post comments on this tracker with your current authentification level.

task #1039: field transition: other field update

Submitted by:  Mathieu Roy <yeupou>
Submitted on:  Wed 10 Nov 2004 01:44:55 PM UTC  
 
Should Start On: Tue 09 Nov 2004 11:00:00 PM UTCShould be Finished on: Mon 15 Nov 2004 11:00:00 PM UTC
Category: Web FrontendStatus: Done
Priority: 5 - ImmediatePlanned Release: 
Assigned to: Mathieu Roy <yeupou>Open/Closed: Closed
Privacy: PublicFor/By: None

Thu 11 Nov 2004 04:15:53 PM UTC, comment #4:

Considering the current extremely low usage of "assign_to" update possibility at LCG Savannah, we will not write an update script, doing it by hand should be faster.

Mathieu Roy <yeupou>
Project AdministratorIn charge of this item.
Thu 11 Nov 2004 03:59:14 PM UTC, comment #3:
  • Extended "other field update" on field value transition: every

other used select box field can now be updated automatically. But
Savane always respect user choices: automatic update will be
disregarded if the user fill out a specific value.
It required the introduction of the "Default" field value, shown
only at item initially submission, to differenciate what the user
fill and what is did not touched.
A drawback remains: on update, it is not possible to override an
automatic update of a field to let this field untouched.
(task #1039).

Remains the update script.

Mathieu Roy <yeupou>
Project AdministratorIn charge of this item.
Thu 11 Nov 2004 03:12:00 PM UTC, comment #2:

The only solution that make sense is to add a "Default" option for each select box on the initial item post form.4

Mathieu Roy <yeupou>
Project AdministratorIn charge of this item.
Thu 11 Nov 2004 03:11:14 PM UTC, comment #1:

Allow extended other field update on field value transition (task #1039). To issues remains: script to update database of savane 1.0.4 (which one allowed update of the assigned to field) ; on item submission, we cannot be sure that someone filled a value on purpose or just kept the default, no
# way to guess what would be the default value (there may be a way, trying to find out
# what would be the first entry on the text field. But what if this person really
# meant this value?

Mathieu Roy <yeupou>
Project AdministratorIn charge of this item.
Wed 10 Nov 2004 01:44:55 PM UTC, original submission:

Currently field transition allows update of the assign_to field.
Field transition will be extended so any used field can be update.

It implies creation of a new table.
It implies update SQL script that will have to automatically add any "assign_to" value into this new field.

Mathieu Roy <yeupou>
Project AdministratorIn charge of this item.

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one

Digest:
   task dependencies.

 

Carbon-Copy List
  • -unavailable- added by yeupou (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 3 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Thu 11 Nov 2004 04:15:53 PM UTCyeupouStatusNone=>Done
      Open/ClosedOpen=>Closed
    Wed 10 Nov 2004 01:45:33 PM UTCyeupouDependencies-=>task # is dependent
    Show feedback again

    Back to the top


    Powered by Savane 3.1-cleanup