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.

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

Regular email updates for project managers (fixes #1377) #1647

Closed
wants to merge 26 commits into from

Conversation

fitoria
Copy link
Contributor

@fitoria fitoria commented May 29, 2019

No description provided.

fitoria and others added 5 commits May 10, 2019 11:55
whole node_modules dir, it uses less CPU this way.
> 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
@xamanu xamanu added this to the 3.4 Release milestone May 30, 2019
xamanu and others added 21 commits May 30, 2019 10:21
Correct time calculations in user profile
…ation

Allow expert validators to classify mapping issues
* 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)
Mapper-level icons and encouragement messages
* 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
Include additional fields on tests
* use cheaper rds instances for non production stacks

* configurable min/max
* 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
Fix tasks annotations and add tasks details
…onwer

Transfer project to new owner feature, fixes #1341
…stamps

Show expert users ISO8601 timestamps on hover
@xamanu xamanu force-pushed the feature/1377-managers-mail-updates branch from ccd0152 to f13d089 Compare June 5, 2019 12:59
@xamanu
Copy link
Contributor

xamanu commented Jun 5, 2019

Rebased and cleaned commits today.

I have some remarks on this, which i wrote in #1377 (comment). Basically to implement the surroundings that a user and admins needs to deal with such messages:

  • Settings page to opt out of all emails and a way opt-out per project.
  • Link in the email footer to the "email preferences".
  • Per default, disable (or send to log) automatic messages. An let opt-in on certain deployments, like live. We probably don't want to send emails to project managers from the staging or a local developers' machines imp

@xamanu xamanu changed the title Fixes #1377 managers mail updates Regular e-mail updates for project managers (fixes #1377) Jun 5, 2019
@xamanu xamanu changed the title Regular e-mail updates for project managers (fixes #1377) Regular email updates for project managers (fixes #1377) Jun 5, 2019
@xamanu xamanu modified the milestones: 3.4 Release, 4.0 Release Jun 25, 2019
@xamanu xamanu modified the milestones: 4.0 Release, 4.1 Release Dec 12, 2019
@xamanu xamanu added this to Backlog in Roadmap - Archived via automation Dec 12, 2019
@xamanu xamanu moved this from Backlog to In Progress in Roadmap - Archived Dec 12, 2019
@xamanu xamanu moved this from In Progress to Backlog in Roadmap - Archived Dec 12, 2019
@willemarcel willemarcel modified the milestones: 4.1.0 Release, 4.2.0 Jul 17, 2020
@Aadesh-Baral
Copy link
Contributor

Reworked on #1935.

@Aadesh-Baral Aadesh-Baral deleted the feature/1377-managers-mail-updates branch July 13, 2022 07:39
@Aadesh-Baral Aadesh-Baral restored the feature/1377-managers-mail-updates branch July 31, 2022 08:14
@Aadesh-Baral Aadesh-Baral deleted the feature/1377-managers-mail-updates branch August 17, 2022 08:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Roadmap - Archived
  
Product Backlog
Development

Successfully merging this pull request may close these issues.

None yet

9 participants