View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 0
IDProjectCategoryView StatusDate SubmittedLast Update
07385Feature requestsImport/Exportpublic2010-01-22 05:242021-11-09 11:05
Reporteruser1Assigned Togalads  
PrioritynormalSeverityfeature 
Status closedResolutionfixed 
Summary07385: Handling of the "additional attribute fields" should be made more safe
Description

Additional token attribute fields are great, but please add some validation:

  • on import, the additional attribute fields should be created automatically; if not, give a warning

  • when using additional attribute fields as placeholders for replacements (e.g. email), there should be a warning plus abort the sending procedure in the cast that the attribute field does not exist in the database

  • additional attribute fields should be recreated when importing surveys

Additional Information

A possible solution: Add checks
1) when importing tokens, give a warning (or create additional attribute fields)

2) before sending the mail, check the placeholders; give a warning and do not send the mail if a placeholder is undefined (i.e. not present in the data model)

3) when importing a survey, create the token attribute fields

TagsNo tags attached.
Bug heat0
Story point estimate
Users affected %

Users monitoring this issue

There are no users monitoring this issue.

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2021-11-09 11:05 galads Assigned To => galads
2021-11-09 11:05 galads Status acknowledged => closed
2021-11-09 11:05 galads Resolution open => fixed