User story #1360
open
Allow Technique to reuse other technique as building blocks / dependencies
Added by Jonathan CLARKE almost 13 years ago.
Updated about 6 years ago.
Category:
Web - Config management
Description
We would like to be able to make technique depends on other techniques to build up complex scenarii.
The notion of dependency here is a little fuzzy: it's more that we want to be able to tell that a technique need something provided by an other technique, but it would make sense to have a common view for such "composed" technique (i.e a way to configure in one go a technique and it's building blocks/dependencies.
A part of the that is already possible with the technique editor and ncf, but we would like to be able to fully reuse existing techniques, or even reuse+give defaults value, or reuse+override to provide a new set of user input.
A dependency would need to be on a technique and on a precise version.
The original ticket was referencing a meeting, but it's mostly irrelevant now (I extracted interesting parts here).
- Estimated time set to 2.00 h
- Status changed from 2 to Discussion
- % Done changed from 0 to 70
- Subject changed from [Réunion] Une PT dépend d'une autre avec des paramètres et une version (spécification) to [Réunion] Une PT dépend d'une autre avec des paramètres et une version: variables multivaluées
- Target version changed from 13 to 14
We need to explicit how to pass a value for multivaluated variables, especially:
- the case where a unique multival. variable in a section with several variables
- the case of a multivaluated version
- every of these cases when they happen for variables contained in multival. sub-sections (the method should be recursive)
These specs should be easy to manipulate for the user, especially in the case of multival. sections, the variables should be grouped by iteration and not by variable name.
- Target version changed from 14 to 16
Specs still need to be completed, as far as I can tell, so this issue is moved forwards to the next run.
- Target version changed from 16 to 10
- Target version changed from 10 to 18
- Target version changed from 18 to 24
- Target version changed from 24 to Ideas (not version specific)
- Category changed from 14 to Web - Config management
- Subject changed from [Réunion] Une PT dépend d'une autre avec des paramètres et une version: variables multivaluées to [Meeting] A PT depends on another one with parameters and a version: multivalued variables
- Description updated (diff)
- Subject changed from [Meeting] A PT depends on another one with parameters and a version: multivalued variables to [Meeting] A technique depends on another one with parameters and a version: multivalued variables
- Subject changed from [Meeting] A technique depends on another one with parameters and a version: multivalued variables to Allow Technique to reuse other technique as building blocks / dependencies
- Description updated (diff)
- Status changed from Discussion to New
- Assignee deleted (
Nicolas CHARLES)
I'm keeping that User story, as it makes sens to thing of dependant techniques, and we should keep it for the record. On the other hand, the Referenced meeting note is totally outdated, and it's not sure at all that we would like to make the dependency notion be implemented like that today. So I will also clause the implementation ticket because it is not relevant anymore.
- Precedes deleted (User story #1361: [Meeting] A technique depends on another one with parameters and a version: multivalued variables (implementation parser))
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by Matthieu CERDA