bitshares / bitshares/bitshares-ui

direct debit spotlight component bug - missing claimable direct debit?

Open
#3,608 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
520
Forks
575
Avg merge
12h 7m
Merged PRs (30d)
5

Description

**Describe the bug**
I created a direct debit where 1 BTS would be transferred to a payee 5 times due to 5 periods of direct debit payments.

After the first period passed, I switched to the payee account and claimed 1 BTS.

I expected there to be a remaining direct debit where 4 BTS would be claimable, however the direct debit table is now blank for both participants in the direct debit.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to the [direct debit](https://wallet.bitshares.org/#/direct-debit) page.
2. Create a direct debit to a second account you control, set 1 BTS to be transferred with 5 periods, submit it.
3. Switch to the payee account, wait for the first period to pass, submit a claim for 1 BTS
4. After claim has submitted, refresh the direct debit page, there shouldn't be a table entry despite 4 BTS remaining after another few mins.

**Expected behavior**
I expected to be able to claim 1 BTS, then another 4 direct debit periods would pass, enabling 4 further claiming periods.

**Screenshots**
See steps: https://hive.blog/hive-120117/@nftea.gallery/creating-a-decentralized-direct-debit-on-the-bitshares-blockchain

**Desktop (please complete the following information):**
- Windows 11, opera

**Additional context**

There's a related direct debit spacing issue in the portfolio:

![image](https://user-images.githubusercontent.com/15861527/205419362-40b04deb-137c-4adc-b8f2-53eb0252a5fe.png)

---

Is the payee only able to claim once? Or should 4 further attempts be possible?

Contributor guide

Open the contributing guide

Research direction

Start at the direct debit page and reproduce the five-period transfer and first claim described in the issue, then inspect the direct debit spotlight component and the related portfolio display. Done means the remaining four claimable periods remain visible and can be claimed after the first period.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
blockchain, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.