Skip to content

FOUR-12450: Filter only the Projects that belong to the User #5666

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

Merged
merged 2 commits into from
Nov 29, 2023

Conversation

estebangallego
Copy link
Contributor

@estebangallego estebangallego commented Nov 18, 2023

Issue & Reproduction Steps

Users without Project ownership can view all projects in the filter.

Steps to Reproduce:

  1. Log in with the admin user.
  2. Create several projects with the admin user.
  3. Log out.
  4. Log in with a different user.
  5. Create additional projects with the second user.
  6. Click on "Projects."
  7. Notice that all projects are visible, not just the ones created by the first user.
  8. Click on the project filter.

Current Behavior:
All created projects are displayed in the project filter, regardless of ownership.

Expected Behavior:
The filter should only display projects that belong to the logged-in user.

Solution

  • Modify the filter to show only the projects that belong to the currently logged-in user.

How to Test

  1. Follow the reproduction steps.
  2. Ensure that the project filter exclusively displays projects associated with the logged-in user.

Related Tickets & Packages

ci:next

Code Review Checklist

  • I have pulled this code locally and tested it on my instance, along with any associated packages.
  • This code adheres to ProcessMaker Coding Guidelines.
  • This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
  • This solution fixes the bug reported in the original ticket.
  • This solution does not alter the expected output of a component in a way that would break existing Processes.
  • This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
  • This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
  • This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
  • This ticket conforms to the PRD associated with this part of ProcessMaker.

@estebangallego estebangallego changed the base branch from develop to next November 20, 2023 18:22
Copy link

@ryancooley ryancooley merged commit e2c632a into next Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants