Re: Global attribute conditions spread

Hi,

In my eyes this is one of the most typically "mistakes" of  Scarab. Due 
to its adaptability, its not very easy to implement such a feature. In 
many cases you will have to reavise these conditions per module anyways.

cheers

pangkorean schrieb:
> Hi,
> I encounter the same problem also.
> If an global attribute absolutely cannot spread its' conditions into module,
> what use if we configure 'conditionally required' in global attribute?
> Anybody can explain?
>
> Thank you
>
> Regards, pangkorean
>
>
> Juan Diego Moreira wrote:
>   
>> Hello.
>>
>> I have created a new issue type which uses a new global attribute. The 
>> global attribute has been declared to use a set of conditions in order 
>> to decide if it is required or not.
>>
>> The problem arises when I create a new module in which I use the new 
>> issue type, because I see that the conditions declared for the global 
>> attribute used by this issue have disappered in the module, so I have to 
>> manually declare the conditions for the attribute in the issue of the 
>> module.
>>
>> Is there any way to spread the conditions in the global attribute 
>> definition to the copy  of the issue type whenever a new module is 
>> created and the global issue type is imported in the new module?
>>
>> Thanks in advance.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>>
>>     
>
>

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

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