Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ready2go: OSMCha option in task Advanced area #1362

Closed
nrotstan opened this issue Mar 1, 2019 · 1 comment
Closed

ready2go: OSMCha option in task Advanced area #1362

nrotstan opened this issue Mar 1, 2019 · 1 comment
Labels
priority: high status: done type: enhancement Improving an existing functionality
Milestone
3.4 Release

Comments

@nrotstan
Copy link
Contributor

nrotstan commented Mar 1, 2019

Note: this feature has been implemented, but not yet submitted as a PR

  • Add an OSMCha option to the task Advanced area
  • Clicking it opens OSMCha and applies a bounding box filter and a starting date set to the timestamp of the earliest history entry for the task

advanced_osmcha
@pantierra pantierra added type: enhancement Improving an existing functionality priority: medium labels Mar 4, 2019
@zlavergne
Copy link

@nrotstan would this feature be easily implemented at a project level?

nrotstan added a commit that referenced this issue May 9, 2019
@nrotstan
View changesets in OSMCha. Closes #1362
de2e84f 
* Add button to task's Advanced section for viewing a task's changesets
in OSMCha

* Add button for viewing project-wide changesets in OSMCha, visible to
users with validator or higher role (expert or higher for projects that
don't enforce a validator role)

* Add new column to projects for storing an OSMCha filter id that can be
optionally used to load a custom OSMCha filter in place of the standard
project-wide filters for projects that require a more customized set of
filters

* A project's OSMCha filter id can be managed from the Metadata section
when creating or editing a project
@willemarcel willemarcel self-assigned this May 20, 2019
@pantierra pantierra modified the milestones: 3.3 Release, 3.4 Release May 23, 2019
pantierra added a commit that referenced this issue May 30, 2019
@pantierra
Merge pull request #1561 from hotosm/feature/1362-osmcha-integration
ae4ea0f 
View changesets in OSMCha. Closes #1362
fitoria pushed a commit that referenced this issue Jun 3, 2019
@nrotstan @fitoria
View changesets in OSMCha. Closes #1362
6a3aa0c 
* Add button to task's Advanced section for viewing a task's changesets
in OSMCha

* Add button for viewing project-wide changesets in OSMCha, visible to
users with validator or higher role (expert or higher for projects that
don't enforce a validator role)

* Add new column to projects for storing an OSMCha filter id that can be
optionally used to load a custom OSMCha filter in place of the standard
project-wide filters for projects that require a more customized set of
filters

* A project's OSMCha filter id can be managed from the Metadata section
when creating or editing a project
fitoria pushed a commit that referenced this issue Jun 3, 2019
@nrotstan @fitoria
View changesets in OSMCha. Closes #1362
2dd4d33 
* Add button to task's Advanced section for viewing a task's changesets
in OSMCha

* Add button for viewing project-wide changesets in OSMCha, visible to
users with validator or higher role (expert or higher for projects that
don't enforce a validator role)

* Add new column to projects for storing an OSMCha filter id that can be
optionally used to load a custom OSMCha filter in place of the standard
project-wide filters for projects that require a more customized set of
filters

* A project's OSMCha filter id can be managed from the Metadata section
when creating or editing a project
pantierra pushed a commit that referenced this issue Jun 25, 2019
@nrotstan @pantierra
View changesets in OSMCha. Closes #1362
861b662 
* Add button to task's Advanced section for viewing a task's changesets
in OSMCha

* Add button for viewing project-wide changesets in OSMCha, visible to
users with validator or higher role (expert or higher for projects that
don't enforce a validator role)

* Add new column to projects for storing an OSMCha filter id that can be
optionally used to load a custom OSMCha filter in place of the standard
project-wide filters for projects that require a more customized set of
filters

* A project's OSMCha filter id can be managed from the Metadata section
when creating or editing a project
@pantierra pantierra mentioned this issue Jul 8, 2019
Merged
ramyaragupathy pushed a commit that referenced this issue Jul 10, 2019
@JorgeMartinezG @ramyaragupathy
Do not apply cascade deletion on message model
3bfa879 
Change circleci deployment branches

Enable RDS Cloudwatch Logging and transactional logs

Change ASG Policy to Target Request Count threshold

Include into migration a cleanup for task_ids on messages for tasks, which don't exist anymore

Scripts to restore deleted projects

Update translations

Avoid providing standard changeset comment

Add required ResourceLabel param to ASG policy

Optimize gulp watch to only track files inside our project and not the
whole node_modules dir, it uses less CPU this way.

Clean up deprecated windows devops script

Include additional fields on tests

Allow expert validators to classify mapping issues

> Note: this includes a new database migration

* Show validators in expert mode an additional form allowing them to
(optionally) classify the type and number of problems they discover with
mapping work that is leading to invalidation of the task

* Record identified mapping issues in a `task_mapping_issues` database
table

* Display noted mapping issues in the task history immediately below the
invalidation where they were recorded

* Allow mapping issues fixed by the validator on behalf of the mapper
to be noted when marking a task as validated

* Display in the task history when a task was validated with fixes, and
show the identified list of issues addressed by the validator

* Add a new page, accessible from the account-nav dropdown menu, on
which project managers and admins can manage the available mapping-issue
categories

* Seed the mapping-issue categories with a couple of initial categories

* Add server RESTful API endpoints for managing mapping-issue categories

* Add new `mapping_issue_categories` and `task_mapping_issues` database
tables in new migration

* Add support on server for optional inclusion of noted mapping issues
during task validation/invalidation

Remove What is New page

Correct time calculations in user profile (#1571)

Correct time calculations in user profile

Add Task Annotations

Update migration and fix minor default value issue

Mapper-level icons and encouragement messages

* Show a trophy icon in the top-nav in a color representing the
logged-in user's mapping level (bronze, silver, or gold for beginner,
intermediate, or advanced respectively), and also prominently display
user's mapping level on their profile page

* Show message on home page and profile page encouraging mappers to
continue mapping and advance to the next level (or to try validating in
the case of advanced mappers)

View changesets in OSMCha. Closes #1362

* Add button to task's Advanced section for viewing a task's changesets
in OSMCha

* Add button for viewing project-wide changesets in OSMCha, visible to
users with validator or higher role (expert or higher for projects that
don't enforce a validator role)

* Add new column to projects for storing an OSMCha filter id that can be
optionally used to load a custom OSMCha filter in place of the standard
project-wide filters for projects that require a more customized set of
filters

* A project's OSMCha filter id can be managed from the Metadata section
when creating or editing a project

Use smaller RDS instances for non production stacks (#1657)

* use cheaper rds instances for non production stacks

* configurable min/max

Show expert users ISO8601 timestamps on hover

* Users in expert mode can hover over a timestamp to view it in IS08601
format

* Clicking the ISO8601 timestamp copies it to the user's clipboard

* Users who are not in expert mode continue to experience existing
behavior

Transfer project to new owner feature, fixes #1341

Fix tasks annotations and complete with tasks details

Add recommended oauth settings in documentation

Update contributing-code.md

Correct typo in title

Add instruction for local development in setup-development.md

Adding link to user manual on teachosm.org

Add markdown support to task annotations

Support Korean

Update eslint to 4.18.2

Restructure scripts a bit

Review documentation on TM2 migration

Modify deployment for new stack

Modify rds instance size to m5.xlarge

Calculate stats in the database

Fixes: #1720

Enforce Random Task Selection

* Add optional setting to Enforce Random Task Selection in the project's edit page

* If Enforce Random Task Selection is enabled, users will not be able to manually select tasks. They will be required to use the "Select A Random Task" button (does not apply to pm/admins)

* Errors appear if they try to select a task from the map

Closes #1583

Consolidating the stats on tasks

Block read_only user comments on projects

Some documentation and sorting of API tags

Include validators #1685 + Separate time calcs

Restructure the endpoints

Remove additional comma

Update method type

Percentage and Centroid fields

Calculate task status percentages on projects in one central function

Prevent SQL Injection when executing custom SQL

Fixes: #1731

Include automatic trigger for indexing text_searchable

Enforces PM or Admin role on the users that will get a transfered project

Add script to extract strings for translation

Block start mapping and start validating options if email is not set
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority: high status: done type: enhancement Improving an existing functionality
Projects
None yet
Milestone
3.4 Release
Development

No branches or pull requests
4 participants
@pantierra @nrotstan @willemarcel @zlavergne