Continuation In - User Uploaded File - Change Name of it
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
**Describe the bug in current situation**
A clear and concise description of what the bug is.
The Continuation In filing makes the user uploaded a document for review by staff. **These uploaded documents are not visible to other end-users.** This is visible in the system with whatever file name it had on the users computer.
**Request -**
- [ ] display this as something like "User uploaded file" or similar.
Rationale:
- This has caused some confusion during UAT
- Perceived risk of user filename having "naughty words" in the name, or confidential information in the name
This affects both the Filing History entry and the Staff Review screen:


**Link bug to the User Story**
**Impact of this bug**
Describe the impact, i.e. what the impact is, and number of users impacted.
**Chance of Occurring (high/medium/low/very low)**
**Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?**
**Steps to Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**Actual/ observed behavior/ results**
**Expected behavior**
A clear and concise description of what you expected to happen. Use the gherking language.
**Screenshots/ Visual Reference/ Source**
If applicable, add screenshots to help explain your problem. You an use screengrab.
**Root Cause Analysis (RCA) results**
If applicable, document the root cause analysis results for the scenarios. This section is mandatory before the issue can be closed
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the Continuation In Filing History and Staff Review screens in the JavaScript/Vue application and inspect where the uploaded filename is displayed. Verify the current filename behavior, then update both locations to show a generic label such as "User uploaded file" and confirm the label appears in each screen.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100