Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 975
    • Issues 975
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • Core
  • Issues
  • #107

Closed
Open
Opened May 09, 2018 by reneolivo@reneolivo

After creating a new case, the assignee for each activity must be selected manually

Issue

After you create a new case multiples activities are created with it, but the assignee must be manually chosen for each one of them which takes considerable time since this must be done by editing each activity one at a time.

default-assignee-issue

There are references for the roles and relationships that are interesting for the particular case, but those are there for reference, the assignee still must be selected manually.

Solution

Allow administrators to define rules for selecting a default assignee for each one of the activities. The rules would be based on the following options:

  • By relationship to case client (ex: parent, manager, or spouse of case client).
  • User creating the case.
  • Specific contact.
  • No default assignee.

When creating a new case each case activity should be created and assigned based on these rules. The case manager could then modify the assignees as usual.


Core PR: https://github.com/civicrm/civicrm-core/pull/11998

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dev/core#107