Project

General

Profile

Actions

User story #3821

closed

for directives, advertise and set new mandatory fields during technique version migration

Added by Fabrice FLORE-THÉBAULT about 11 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - UI & UX
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

When you migrate a directive to a new technique, and when there are new mandatory fields, they are not set up during migration. Actually you migrate the directive, have no information about mandatory fields, try to save, look at the errors, correct them in an iterative way, and finally have the directive migrated.

It would be much nicer with a migration screen advertising the fact that the new version of the technique has new mandatory field (and name them). I would be even nicer if this screen could help you set these fields.

For instance, give the choice between:

  1. set recommended defaults (explain them)
  2. set a default to be choosed in the list of available choices in case of a list, or let user input the value
  3. leave the new fields empty
Actions #1

Updated by Vincent MEMBRÉ about 11 years ago

  • Assignee set to Jonathan CLARKE
  • Target version set to Ideas (not version specific)

Migrating Directive is quite a heavy pain, we should definitely improve that process.

Lots of changes will come in 2.8 about Techniques, and I hope it will ease the migration process, and at least we should look into this.

Actions #2

Updated by Jonathan CLARKE about 11 years ago

  • Assignee deleted (Jonathan CLARKE)

Agreed, this would be a lot better. The upcoming changes in Techniques for 2.8 will impact how this works, let's see then.

Actions #3

Updated by Benoît PECCATTE over 7 years ago

  • Status changed from New to Rejected

This is now handled properly

Actions

Also available in: Atom PDF