When screens are configured for import, the default Import functionality is in most instances used in the same manner between different imports (and in many cases the import Excels follow a predefined format).As a result end users often find setting up the options on the “Select location of column names and data” part of the import wizard somewhat complex and cumbersome.If the options under “Headers” and “Data” could be preconfigured on subject level in the SF model + an option to skip the entire “Select location of column names and data” (for cases where only one worksheet is used in the import Excel and no data selection is necessary) could be made available, this would make the import easier and quicker to use.
Importing/adding translations and validating translations are tasks that are sometimes attributed to specific persons in the project team that are not developers. This is especially likely to happen when a high number of languages and/or more exotic languages are to be supported.To better support this scenario a formalized translator user group (and underlying roles) in the Software Factory would be beneficial. Users that are part of such a group should have access to the “Translations” menu item and the tasks to generate and translate translation objects and the possibility to import/export translations without having the possibility to change the data-/gui model and functionality.
In the 2021.1 version of the Software Factory storypoints can be attributed to requirements/user stories and hours to work, which is definitely useful. The flexibility/usability of these elements would however be improved if the units of measure could be freely chosen in a future version.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.