"handle as in future" - feature

Open
#105 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
php
Domain
backend, payments

Research direction

No files, tests, or entry points are named. Start by tracing how payment reasons are matched and how campaign status is checked, then identify the existing path for defining automatic handling rules. Done means equivalent or similar reasons and links to closed campaigns produce warnings with an option to define a future automatic rule.

Written by the indexing model from the issue text.

Description

feature needs funding

Sometimes a donor uses online-banking to donate regulary. The bankers order is in many times not recognisable. Therefore it would be useful if civibanking behaves as follows

  • Warn, if a equal (or similar) reason for payment exists in the database
  • Warn, if a reason of payment links to a closed campaign

In this cases civibanking should offer a link to define a rule for handling payments with this specific reason for payment in the future automaticly.

Dominant language
PHP
Stars
22
Forks
45
Avg merge
3d 15h
Merged PRs (30d)
7

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Project60/org.project60.banking

All issues in Project60/org.project60.banking

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.