Problem/Motivation

Burndown has a great feature of dynamically creating project specific perms for creation, edit, and delete. It would be nice to extend that granularity to Viewing the project.
Example:
Project "Public Project A" could be viewed by anyone with anonymous role
Project "Private Project B" could be viewed by logged in users
Project "Super Private Project C" and only be viewed by administrator and staff roles

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork burndown-3605085

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

swirt created an issue. See original summary.

swirt opened merge request !28

swirt’s picture

swirt
he/him
Primary language English
commented

This MR is working correctly now.

The approach should be 100% backward compatible as it only kicks in if people add a project specific view permission. This does not alter any action related api access. This only allows to optionally control "view" access to

  1. boards
  2. backlogs
  3. completed
  4. tasks

jeremylichtman’s picture

jeremylichtman commented
Status: Active » Fixed

Merged, and added to tag 1.0.59.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

swirt’s picture

swirt
he/him
Primary language English
commented

Thank you @jeremylichtman, you are fast. I hadn't even had a chance to add QA steps ;)

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.