DealerApp

Roland Pfeifer
17/12/2017

Dealer App Requirements

The basic requirement for an issue log with CRUD functionality can be met by opensource issue trackers like redmine. At the heart they provide the core capabilities

  • task tracking, tasks can be custom defined as required. Complaint, Bug, SR, TT
  • project including subproject to define the structure of collaboration and reporting
  • roles and permission: in addition to basic CRUD permissions also more advanced roles possible.
  • workflow to manage the process of tasks and status

Environment for POC

URL: https://dealerapp.easyredmine.com

User logins: dealer1, dealer2, sales1, rgm

Mobile Client App1: Redmine-by-easy

Mobile Client App2: RedminePM

Mobile Client App3 (REST API): OpsGenie

Usecase: Mobile, Web

Mobile access by respective users through the app, enter url and user/password. EasyRedmine currently installed in the cloud. On-premise installation of redmine is present already can be used as well.

Webaccess through URL, use https if available

Usecase: Issue Log

The issue log uses the core task tracker in redmine. The OOTB fields cover

  • Id: Auto-generated
  • Log date: Start date
  • description: free text, can create custom tasks/dropdown list for Classification
  • resolution date: Can define, duedate, milestones, status date
  • resolution description: as free description, can also be modelled as status types.

In addition following functioanlity comes OOTB

  • definition of workflows, status (i.e. onlt RGM can close issue, sales can assign issue to dealer not opposite)

Usecase: Dealer log: create, read, update only own records

Implemented through roles/permission dealer role

  • Tasks visibility: Tasks created by, assigned or watched by user
  • View task (L)
  • Create task
  • set task where user is authour as private
  • edit owns comments
  • edit tasks where user is author
  • view coworker list (restricted by user types visible, none, only himself)
  • workflow configured for NEW, IN PROGRESS, SUPERVISOR REVIEW

Usecase: Sales, create on behalf of dealer, edit not delete dealer logs

Implemented through roles/permission sales role

  • View tasks
  • Create tasks
  • edit tasks
  • Add coworker
  • delete coworker
  • view coworkerlist (can view usertypes of dealer to create/assign issue to a dealer)
  • workflow configured for NEW, ASSIGN_TO_COWORKER, IN PROGRESS, SUPERVISOR REVIEW

Usecase: RGM, full access

Implemented through default project manager role for subproject = salesregion Task visibility: all non privat task of the project Member managment for sales and dealer Workflow: Only RGM can close issue, status DONE

Usecase: Enhanced structure for DealerID, DealerUserID

No implemented in the POC but can be done through UserGroup, one UserGroup per DealerID and DealerUserID assigned to respective Group can see each others.