Skip to content

Conversation

@devmiguelangel
Copy link
Contributor

Issue & Reproduction Steps

Describe the issue this ticket solves and describe how to reproduce the issue (please attach any fixtures used to reproduce the issue).

Solution

  • List the changes you've introduced to solve the issue.

How to Test

Describe how to test that this solution works.

Related Tickets & Packages

  • Link to any related FOUR tickets, PRDs, or packages

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.

CarliPinell and others added 30 commits December 5, 2024 15:42
…Expressio

 ## Description:
Steps to Reproduce the Issue:
  Open a Request/Case:
Navigate to the ProcessMaker cases and open an existing request (case).
Click on the Reassignment Button:
Locate and click the "Reassignment" button to reassign the case to another user.
  View the Assignment User List:
Observe the list of users displayed in the reassignment dropdown.
  Current Behavior (Issue):
Instead of filtering users as per the regular expression, all users are displayed in the reassignment list.
  Expected Behavior:
The user list should be filtered based on the regular expression condition set in the process.
Only users that match the specified regular expression should appear in the list.
  Impact:
The client expects the user list to be filtered dynamically based on the regular expression condition applied in the process, but it is not working correctly.
  Potentials Fix:
Request the development team to investigate and ensure that the reassignment user list correctly applies the regular expression condition as configured in the process.
  Acceptance criteria:
When having a Rule Expression, the reassignment should only allow to reassign to Admin, Process Manager or the users listed in the Rule Expression list.

 ## Related Tickets & Packages
https://processmaker.atlassian.net/browse/FOUR-23734
nolanpro and others added 28 commits October 27, 2025 17:11
Process Manager - Number of Users to Assign
Fix scheduler when tenants have different db credentials
It is possible to upload dangerous files from Web Entry
FOUR-26661: Implement cases list compoment in the Application Dashboard
FOUR-26568 [47293] Error on parent request even the ABE process shows  completed status
FOUR-25374: 46017 - Slow query in Inbox, lack of index
41600 - Slowness when a user is member of too many groups
Fix memory issues with queue workers
@processmaker-sonarqube
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

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.