#SCB2984 (In progress) required attributes markup does not change when requiredConditions are met during issue edit

*SCB2984 [Enhancement] - required attributes markup does not change when requiredConditions are met during issue edit*

-------------------------------------------------------------------------------
*Reasons for the changes*
-------------------------------------------------------------------------------
  - I started a javascript based runtime condition checker.

** null:  () **


-------------------------------------------------------------------------------
*Personnel changes*
-------------------------------------------------------------------------------
  - Assigned cc:  dabbous     (New) 


-------------------------------------------------------------------------------
*Attribute changes*
-------------------------------------------------------------------------------
  - Priority:  2-High     (New) 
  - Short description:
    "If a conditional attribute is not required on startup of the issue editor,
but while editing the required condition gets eventually fulfilled, then 
the attribute should be immediately marked as required.
The same is true when a conditionally required attribute gets no longer
required during editing. In that case the required marker should disappear
immediately.

Currently the attribute simply keeps its markup as it was upon starting
the editor and only changes it when the issue is edited the next time.
This is very missleading and inconvenient."
  - Summary:  required attributes markup does not change when requiredConditions are met during issue edit     (New) 
  - Status:  Unconfirmed     (New) 
  - Target milestone:  0.23     (New) 
  - Status:  Unconfirmed --> In progress  


*Comment Hussayn Dabbous*

I created a runtime condition checker.
This checker basically uses a javascript based
Observer pattern. The observer fires every time
when an attribute option is changed. 
The "client" part contains of a framework function "conditions_observer()"
which is mostly static (added to layouts/default.vm). 

However there is a fraction of this function, which is generated by velocity
and contains statements dereived from the associated set of
attribute-conditions for the given issue type.

Thus every time an attribute option is fired, the condition checker checks all
available attributes, if the required condition is met ort not and adjusts the
visibility of the required marker accordingly.


-------------------------------------------------------------------------------
Activity generated by Hussayn Dabbous ([email protected]) at 07/14/2009 22:25

[Scarab]: http://www.solitone.org/scarab/issues/id/SCB2984

------------------------------------------------------
http://scarab.tigris.org/ds/viewMessage.do?dsForumId=458&dsMessageId=2371328

To unsubscribe from this discussion, e-mail: [[email protected]].