Conduct research into compression libraries that would allow the compression of video files being sent

Ideal Hours: 2 hours
Related Stories: #34

In the toolbar that results from long-pressing a message, add an option to mark a message as unread.

Ideal hours: 5 hours
Related Story: #36

In the release 2 document, add a description in the appropriate sections about the marking a message as unread feature.

Ideal hours: 0.5 hours
Related stories: #36

On your local machine, set up the development environment required for the project. Clone the app and make sure it runs in your development environment.

Ideal hours: 6 (1 hour per developer)

Related Stories: #6

• Ben
• Lori
• Claudia
• Bryce
• Jacob
• Sam

In the conversation view activity, implement a feature that allows the user to swipe right across the screen with their finger. Integrate a swiping animation to go along with this feature.

Ideal Hours: 10 hours
Related Stories: #10

Implement basic tests for the code we wrote

Ideal Hours: 3 Hours
Related Stories: #18 #19 #20

Unit Tests:

• Done

Acceptance Testing:

• Done

UI Tests:

• Done

Document mockups and changes in the release document.

Ideal Hours: 2 hours
Related Story: #38

Implement the ability to swipe left on a conversation node in the conversation list view. The animation should be similar to that of archive but with a different icon.

Ideal hours: 7 hours

Related stories: #9

As a user, I wish for the application to be protected by a fingerprint authentication in order to add another layer of security to my messages.

Priority: 3/4
Risk: 3/4
Story Points: 5

Demo Steps (acceptance criteria):

1. Access the Signal application, and in the security settings, turn on fingerprint authentication
2. Close the application
3. Reopen the application. It will ask you to authenticate with a fingerprint
   3.1 If the fingerprint is invalid, the application will ask for the backup passcode
4. Access should be granted for the proper print or passcode

Subtasks

#65 UI Mockup for fingerprint auth @lori-dalkin
#81 Implement UI and logic for fingerprint settings for enabled/disabled @lori-dalkin
#66 Import fingerprint api and implement backend logic @BDSchoeler
#67 Implement UI for fingerprint auth @BDSchoeler
#68 Fingerprint Authentication Tests @lori-dalkin @BDSchoeler
#69 Fingerprint authentication documentation @lori-dalkin @BDSchoeler

Acceptance Tests

Auth = Authentication

Mockups

• Settings Disabled
  

• Settings Enabled
  

• Fingerprint Authorization Homescreen
  

In the release Document, write a paragraph describing the extracted architecture.

Ideal hours: 0.5

Related Stories: #3

Connect the Signal fork to Jenkins for continuous integration

Ideal hours: 1

Related Story: #1

Implement Unit and Acceptance tests for marking a message as unread.

• Unit tests

• Acceptance tests

Ideal Hours: 6 hours
Related Stories: #36

Upon swiping right in the conversation view activity, trigger the back button functionality to take the user back to the conversation list view.

Ideal Hours: 5 hours
Related Stories: #10

Within the AndroidTest directory, there are currently existing test which are failing due to unknown reasons. These must be fixed in order to run espresso tests for the application.

Ideal Hours: 2h
Related Story: #56

As a software developer, I want a local development and test environment in order to be able to implement new features and to develop and run tests for these new features.

Priority: 2/4 (medium)
Risk: 1/4 (low)
Story Points: 1

Subtasks: #7

Implement test code to test that the back button functionality is triggered from the conversation list view upon swiping (if possible)

Ideal Hours: 5 hours
Related Stories: #10

As a user, I wish to have the option to mark a message as unread in order to bring back the notification so that I may have a reminder to re-read this message at a later time.

NOTE: This will have no effect on the recipient's view of the message's read status.

Priority: 2/4
Risk: 2/4
Story Points: 3

Demo steps (acceptance criteria):

1. Open the Signal Application and access a conversation with an unread message
2. Note that the message notification has been cleared.
3. Long press a message
4. In the resulting toolbar, choose to mark a message as unread
5. Note that the unread message notification will again appear

Subtasks

#51 UI Mockup for marking a message as unread
#52 Implement the change to the Read field
#53 Add menu option to mark a message as unread
#54 Test marking as unread
#55 Document marking as unread
#70 Mark messages as unread look different
#71 Allow user to unmark as unread

Acceptance Tests

On the conversation settings screen we want users to be able to edit other people's names.

Ideal Hours: 3h
Related Stories: #11

As a user, I want to be able to swipe across the screen to delete a conversation from history.

Demo Steps (Acceptance Criteria)

• Open Signal application to conversation list view.
• Swipe left on desired conversation to delete.
• Conversation should no longer appear in the conversation list view nor the archived conversation list view.

Sub Tasks
#21 Locate conversation view activity (1.5 hr)
#22 Implement swiping left on a conversation node (7 hrs)
#23 Connect delete function with swiping. (3 hrs)
#24 Develop tests for delete functionality (3 hrs)
#28 Animate swipe left action*
#29 Change the display message when deleting*

*Branched off subtasks from #22

Acceptance Tests:

Priority: 3/4 (medium)
Risk: 2/4 (medium)
Story Points: 5

Implement Tests (Unit tests, acceptance tests) for video compression feature

• Unit Test
• Acceptance Test

Ideal Hours: 6 hours
Related Stories: #34

Take screenshots of the existing UI, and add to these screenshots specifics for pinning messages to a conversation

Ideal Hours: 2 hours
Related Story: #38

As a user, I want to be able to rename my signal contacts in order to customize my contact list.

Demo Steps (Acceptance Criteria)

• Be able to select a contact and add a nickname.
• Contacts with nicknames should display nicknames instead of contact names.
• Nicknames should be persistent within the application
• Polling for contact information should not affect nicknames.

Sub-tasks

• #18 Make name editable on the conversation settings screen
• #19 Save nickname after the user confirms
• #20 Load nickname wherever it's needed
• #30 Write appropriate tests

Priority: 4/4 (high)
Risk: 3/4 (medium)
Story Points: 8

Acceptance Tests:

As a user, I wish to have my videos be compressed in order to send video media quicking and using less data.

Priority: 4/4
Risk: 2/4
Story Points: 8

Demo Steps (Acceptance Criteria)

1. Open the Signal Application and open an existing conversation
2. Select to attach a video attachment
3. Select an existing video, for which you know the size
4. Send the video as an attachment
5. Verify that the size of the video has been compressed upon sending

Subtasks:

#46 Research Video Compression Libraries @BDSchoeler @samantha-kerr
#47 Implement Compression for Outgoing Videos @BDSchoeler @samantha-kerr
#48 Implement Decompression for Incoming Videos (not used)
#49 Test Video Compression @BDSchoeler @samantha-kerr
#50 Document Video Compression @samantha-kerr

Acceptance Tests

From the existing Signal project (latest release) extract the components and create a diagram. Include diagrams (or link to documents) in the release document.

Ideal hours: 4

Related Story: #3

Whenever the application needs to load a person's name it should check if there's an existing nickname and display it if it exists.

Ideal Hours: 5h
Related Stories: #11

Implement a function which updates the database to change the read flag on the selected Conversation Item.

Ideal Hours: 5 hours
Related Story: #36

Using the library obtained through research, implement compression for outgoing attachments.

Ideal Hours: 5 hours
Related Story: #34

In the code base, locate where the conversation list view, and see how a conversation can be archived.

Ideal hours: 1.5 hours

• Bryce
• Lori

Related stories: #9

Upon swiping left in the conversation list view activity, trigger the delete conversation method which will delete the conversation that you swipped.

Ideal Hours: 3 hours
Related Stories: #9

Using the component diagram, make a rough estimation of the Activity architecture of the application.
Include diagrams (or link to documents) in the release document.

Ideal hours: 2

Related Story: #3

When the user confirms that they are done editing the name it should save properly so that the information can persist.

Ideal Hours: 5h
Related Stories: #11

In the Release Document, Infrastructure Section, document the use of Jenkins over the use of Jenkins.

Ideal hours: 0.5

Related Stories: #1

As a user, I wish to be able to pin one conversation to the top of the Conversation List, in order to more easily access this conversation. This may be a conversation that is very important, or one that I do not want to have to spend time looking for.

Demo steps (Acceptance criteria)

Subtasks

Priority:
Risk:
Story points:

Implement UI, Acceptance and Unit tests for story #38 and all related subtasks to ensure quality of the deliverable.

Ideal Hours: 5 hours
Related Story: #38

Using the library researched, implement decompression for all incoming video attachments.

Ideal Hours: 5 hours
Related Stories: #34

As a user, I wish to have the ability to search for text within a conversation in order to more easily find a particular message.

Priority: 4/4
Risk: 3/4
Story Points: 8

Demo Steps (acceptance criteria):

1. Open the Signal application and access an existing conversation
2. Select the option to search from the conversation menu
3. Enter a search term
4. Check the resulting messages containing your search term

Subtasks

#59 Searching UI Mockup @samantha-kerr @claudds
#60 Search box and Icon @claudds
#61 Apply search term to messages @jacobrs
#62 UI for highlighting searched terms @samantha-kerr
#63 Tests for searching @samantha-kerr @jacobrs @claudds
#64 Documentation for searching @samantha-kerr @claudds

Acceptance Tests

Mockups

As a software developer, I want to research whether or not the application imports and stores contact information in order to prepare for the next sprint's development.

Priority: 2/4 (medium)
Risk: 1/4 (low)
Story points: 1

Subtask to build an activity that will display all pinned messages of a specific convo.

Ideal Hours: 3 hours
Related Story: #38

As a user, I wish to have the ability to pin messages in a conversation to the bottom of the conversation in order to more easily access these messages.

Priority: 3/4
Risk: 3/4
Story Points: 5

Demo Steps (acceptance criteria):

1. Open the Signal Application and access a conversation
2. Long Press a single message. A toolbar will appear at the top of the screen
3. Choose to pin the message
4. Click on settings (three dots) and select "View Pinned" to go to Pinned Messages Activity View.

Subtasks:

#45 Pinned Message UI Mockup @lori-dalkin
#41 Pinned Message Elements in Conversation View Activity @lori-dalkin
#42 Load all pinned messages within new Pinned Messages activity @jacobrs
#43 Testing pinned messages @lori-dalkin & @jacobrs
#44 Documenting Pinned Messages feature @lori-dalkin & @jacobrs

Acceptance Tests

Final Design

• Pin and Unpin Icons
  
  
• Small pin icon for messages
  
• Accessing Pinned Messages Activity
  
  

Implement test code to test that the conversation is properly deleted, or that the method is properly called.

Ideal Hours: 3 hours
Related Stories: #9

Add menu icon for pinning a message.
Implement logic that will mark messages as pinned in the local database on icon click.
Add pinned indicator icon for individual pinned messages.

Ideal Hours: 5 hours
Related Story: #38

Pseudo-Story 1:
As a developer, I wish to have continuous integration set up in order to be aware of the state of the builds and test environment for my project

Priority: 2/4 (medium)
Risk: 1/5 (low)
Story Points: 2

Subtasks: #2 #12

As a developer, I wish to have access to the Espresso testing framework in order to more easily develop automated acceptance and UI tests.

Currently, there are flawed tests within the AndroidTest suite for the Signal Application. Registration through a phone number also hinders the ability to perform Espresso tests as there is no existing test phone number known.

Demo Steps (acceptance criteria)

1. Select an Espresso test to run
2. Run the appropriate espresso test successfully

Subtasks

#57 Fix Existing Espresso Tests
#58 Bypass Phone Number Registration

Acceptance Tests

Priority: 4/4
Risk: 2/4
Story Points: 3

Change the display message from "archived conversation" to "deleted conversation" when deleting conversation.

Ideal Hours: 2 hours
Related Stories: #9

Using screenshots of the current application, create a mockup UI for marking a message as unread

Ideal Hours: 1.5 hours
Related stories: #36

As a user, while I am in a conversation, I want to be able to swipe to go back to the conversation list view.

Demo Steps:

• Open Signal application to conversation list view.
• Select a conversation to open.
• From this conversation, swipe right to return to the conversation list view

Sub Tasks

• #14 Locate conversation list view and conversation view activity.
• #15 Implement swiping right in the conversation view activity.
• #16 Trigger back button functionality on swipe right from conversation view activity.
• #17 Develop tests for back button triggering.

Priority: 2/4 (medium)
Risk: 2/4 (medium)
Story Points: 5

Acceptance Tests:

The animation should be similar to that of archive but with a different icon.

Ideal hours: 4 hours. (Hours remaining from #22 )
Related stories: #9

In the code base, locate where the conversation list view and conversation view activities are, and how they connect to each other

Ideal hours: 2.5 hours

• Claudia
• Sam

Related stories: #10

Add information about the implementation of this feature to the relevant sections of the release document

Ideal hours: 1 hour
related Stories: #34

As a software developer, I would like to have an overview of Signal's software architecture in order to implement new features in the proper place and enhance this architecture.

Priority: 4/4 (High)
Risk: 3/4 (medium)
Story Points: 5

Subtasks: #4 #5