bcgov / bcgov/foi-flow

Adding and removing files to email correspondence

Open
#390 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Story
Dominant language
Python
Stars
8
Forks
2
Avg merge
14h 34m
Merged PRs (30d)
46

Description

  • As a FOI Analyst
  • I want to add or remove files to my emails
  • so that I can include files in correspondence about the FOI request

Assumptions & Scope
What are the assumptions for this story?
Users should be allowed to upload multiple files using the functionality noted below.
Maximum file size is in line with IAO standards (20mb) - For MVP, any files larger can be shared by an alternate means

What is in and not in scope?

Acceptance Criteria

Scenario 1: Adding a file using the Add Files button

Scenario 2: Adding a file by dragging and drop

Scenario 3: Removing file attachment

Scenario 4: Removing multiple file attachments

Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)

Validation Rules? (If yes, list here)

Definition of Ready

  1. Is there a well articulated User Story?
  2. Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
  3. If there is a user interface, is there a design?
  4. Does the user story need user research/validation?
  5. Does this User Story needs stakeholder approval?
  6. Design / Solution accepted by Product Owner
  7. Is this user story small enough to be completed in a Sprint? Should it be split?
  8. Are the dependencies known/ understood? (technical, business, regulatory/policy)
  9. Has the story been estimated?

Definition of Done

  1. Passes developer unit tests
  2. Passes peer code review
  3. If there's a user interface, passes UX assurance
  4. Passes QA of Acceptance Criteria with verification in Dev and Test
  5. Confirm Test cases built and succeeding
  6. No regression test failures
  7. Test coverage acceptable by Product Owner
  8. Ticket ready to be merged to master or story branch
  9. Developer to list Config changes/ Update documents and designs
  10. Can be demoed in Sprint Review
  11. Tagged as part of a Release
  12. Feature flagged if required
  13. Change Management activities done?

Contributor guide

Open the contributing guide

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.

Research direction

Start at the Email Details page within the Correspondence page and review the linked designs for the empty and attached-file states. Trace the existing correspondence email flow and its file-upload component, then verify file selection, drag-and-drop, removal, multiple attachments, and the 20 MB limit against the four scenarios.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 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.