GAP-UAT: Provide text in Attachment nodes to define acceptable file uploads for users
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 14
Description
Gap Details
Found by: Iterative UAT SMES (maria if lead is needed)
Ticket being tested: #1644
Sprint#: 10
Test case#: 10.05
Internet Browser used: Chrome mostly - may be others
Gap Description:
Text disclosing upload parameters is not provided in the Attachments section. Since UAT group didn't know what number, kind of files or file sizes are uploadable, they tried uploading multiples and varied types and sizes.
- all multiple uploads failed
- single kmz files failed.
- some single jpgs failed while others succeeded.
Acceptable file types are currently still being decided by the team, so this text will have to wait until that functionality is finalized and built out.
Screenshots (if applicable):
Rationale / Business Context for Change:
Basic text stating acceptable number of uploads, file sizes, and file types must be provided to reduce inquiries to branch or frustrated users.
Proposed Solution (if applicable):
enter text under file upload section title
Steps to Reproduce / Get us to where you were
- From the left hand sidebar, go to the Internal Permit Dashboard
- Select any application from the dash and scroll down to Tasks
- Select 'Messages' under any of the tasks'
- Look to Attachments' file upload section
Acceptance Criteria
A checkbox list of measurable, quantifiable items that must be met before the story is considered Done.
- acceptable file upload parameters are visually available in file upload section
- parameters include number of files accepted, sizes accepted, and types
Test Case Drafts for QA/UAT
- From the left hand sidebar, go to the Internal Permit Dashboard
- Select any application from the dash and scroll down to Tasks
- Select 'Messages' under any of the tasks'
- Look to the Attachments' file upload section
- Confirm guidance text is available somewhere in the attachments section
- Confirm guidance defines number of files accepted, sizes accepted, and types
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the Internal Permit Dashboard flow: open an application, go to Tasks, select Messages, and inspect the Attachments upload section. Confirm the team’s final upload limits, then add visible guidance covering the accepted number of files, sizes, and types; verify each item through the listed UAT steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100