Project

General

Profile

Actions

action #671

closed

Alternative workflow for reimbursements that have been rejected

Added by ancorgs over 10 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Development
Target version:
Start date:
2013-08-27
Due date:
% Done:

100%

Estimated time:
8.00 h

Description

Currently, when a reimbursement have been rejected by administratives, it needs to be approved again by the TSP members and accepted again by the user. In most cases, prior to that, the reimbursement is rolled back to the requester for corrections, which means reject -> roll back -> submit (again) -> approve (again) -> accept (again).

Even if it makes sense from a workflow perspective is hard to understand for users. We need to either make it more intuitive, either to design an alternative (shorter) workflow for reimbursements that have been rejected.

Actions #1

Updated by ancorgs over 10 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

After considering several alternatives and studying the real cases, turns out that the main problem was that users got confused about attaching the new "signed acceptance" document. So instead of changing the whole workflow (which is quite risky), more information have been added to the interface to clarify that point.

Actions #2

Updated by ancorgs about 10 years ago

  • Status changed from Closed to In Progress
  • Target version changed from Version 0.9 to Version 1.0rc

Changes is the interface were not enough. People is still confusing even when no rejection is involved. Evaluating alternatives again.

Actions #3

Updated by ancorgs about 10 years ago

A lot of time invested designing a new reimbursement process (which also implies other changes at some levels) and mailing a detailed explanation of the proposal to TSP Committee.

Actions #4

Updated by ancorgs almost 10 years ago

Finally, during oSC'14 I found the time to sit with the Committee and review the proposed workflow. I got their approval, so I implemented the new workflow and presented it at https://www.youtube.com/watch?v=gDA4ccqp570

The issue is still open because, although the test suite was adapted, it still lacks specific tests for a newly introduced functionality related to the calculation of the authorized amount.

Actions #5

Updated by ancorgs almost 10 years ago

  • Status changed from In Progress to Closed

Test cases and better documentation finally written. Version 0.9.7 deployed in production.

Actions

Also available in: Atom PDF