Prod release 3.0.0 #576
Merged
Prod release 3.0.0 #576
Conversation
This file contains hidden or 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
Feature/bulk milestone updates
- return all the milestones instead of object with "created", "updated" and "deleted" milestones
- disable logic of automatic updates other fields of milestones when we update some fields
allow non-admin users to set "completionDate" and "actualStartDate" during milestone updating if they are not yet set
# Conflicts: # docs/Project API.postman_collection.json # package-lock.json
…vice into develop
# Conflicts: # src/routes/milestones/update.js
- also removed some commands which are not needed from package.json
Fixed Local setup for windows
- use single config file `.env` without `local.js` - moved light docker-compose file to a separate dir, and make full docker-compose file to be the main one - renamed some npm commands to be more simple and with logical names - mention Windows support - make up to date guide on how to run Project Services with Docker
using up to date metadata from DEV
Permissions for attachments
…oint. - Revert test and use another regular user.
They not always work correctly.
Fix for Issue #560 Don't return members to user without enough permission
Fix for Issue #561 Return empty invites for user without enough permission
# Conflicts: # src/permissions/constants.js # src/routes/projects/get.js # src/routes/projects/get.spec.js # src/routes/projects/list.js # src/routes/projects/list.spec.js
…s-permission-fixes Members & invites permission fixes
Otherwise we cannot use different environment for "test" command and when runnig locally.
# Conflicts: # src/routes/milestones/create.js # src/routes/milestones/delete.js # src/routes/milestones/update.js
Currently, if we restart computer or Docker App, all other containers would be stopped, but rabbitmq would be restarted. We have to be consistent there, either restart all or none. So we don't restart rabbitmq also.
This reverts commit f1d0f90.
- don't raise status change event on every milestone update - removed/commented redundant code for raising events during cascading updates
…-updates Bulk milestone updates
This reverts commit f6cad04.
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.
No description provided.