IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
The user should not be able to edit a survey if they do not have permission to edit the job template. I've added a check if the mode is 'edit' to see if the can_edit flag is false.
There was a discrepency between save states in the survey maker when creating a new job template. I had to make some changes to how we 'save' survey's when creating job templates. Now survey info is stored in a seperate object and then stored in the scope when the user clicks save. It used to all be stored in teh scope object.
Added 'noLink' option to the list view for the portal job templates, so that the list has a default sort-by option but does not contain links to other pages.
adding noLink option which will override any other options to make a list column an href. This is useful when using the 'key' attribute, which sorts a list and includes links on the items. Now there is a way to override this feature. This is for portal mode and used in custom inv scripts as well.
The host events modal needs to have escape characters for tag elements in case a user tries to inject html code into the arguements of the host events.
If the session times out, and the user attempts to open a modal dialog, then it must be closed due to the fact that bootstrap modals do not work with more than one modal open. The login modal is a bootstrap modal so all other modals need to be closed when it is shown.
The SCM type for the projects page was broken when we sorted the drop down options by value. There was no value for 'manual' projects. I had to insert the word 'manual' where it was expecting a blank sting and then remove the word manual before saving the job template to the API
if the user saved a job template with empty extra variables and the Parse as option as JSON, then the UI crapped out. I added a check to make sure the default string is '{}' if the user submits an empty field.
