fix FS#2134 adapt selects when moving task to other project #704
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
get global, current project and target project properties id/value pairs separated
When user tries moving a task to other project, the selects now show id/value pairs of global, current project, and target project if there would be invalid task values stored unchanged. Gives the user a chance to change to allowed ids/values when moving a task between projects (without copying the task)
in database to integer 0 because field os_id is currently defined with NOT NULL
set just a basic translation of optgroups for most selects when moving a task to other project
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allows a user who wants to move a task to another project to choose legal entries for the task properties.
fixes FS#2134