cis-412-spring-2015 / frontend Goto Github PK

obsolete

As a developer I need to be able to have tech stack running on my windows machine and create documentation for it, so that I will be able to run Hospital Run on my machine and have a "how to" for my team members to see.

• Get Technology Stack working -> 12hr
• Download Ember Inspector from the Chrome Web Store -> 20min
• Show that on your computer HospitalRun works -> 20min
• Add your name to the Reports Archive (index) Template file in a paragraph tag to show that you have looked through the code, and have the tech stack working. -> 10min
• Create documentation for a Windows machine -> 50min
• Push changes up to server. (please make sure that your code it not broken!) -> 20min

obsolete

obsolete

Chriatianity Explored Class:

• Sessions
• Participants
• Graduates
• Participants seeking Continued Ed.
• Create View
• Support partial data collection
• Edit Data
• Save Data
• Validate data

Faith Declarations:

• Name ( First/Last )
• Date
• Gender
• Age
• Address
• Religious Affiliation (None, Catholic, Muslim, Protestant, Recommitment, Other)
• Present Activity (Bedside Presentations, Playroom Presentations, Jesus Film, Open Air Meetings, Mobile Clinic Outreach, Door to Door Evangelical, Other)
• Create View
• Support partial data collection
• View All Names
• Support Sorting by each field
• Support Search by each field
• Edit All Names/data
• Save Data
• Validation

• Look into how the module has been created thus far
• Look through the existing code to learn the conventions
• Create a view that shows up when someone clicks the 'Hospital' Tab Under the 'New Report'/'In Progress Report' section of the module.

Referencing Issue: #5

obsolete

As one of the Cure Interns who has spend a lot of time with the products we will be using this semester, I need to make sure that the rest of the Cure team is up to speed with what is going on, so that Peter and I are no longer the only ones who know what is going on.

• get everyone up to speed with Github 7 hours (@neongreenfruit)
• meet with Nejmeh about backlog 30 minutes (@neongreenfruit)
• Set up Ubuntu/Windows documentation - 12 Hours (@Falconvaulter)

• Create View
• Four tabs
• Staff
  • View all Staff
  • Add
    • Names
    • Church Affiliation (Auto from last month)
    • Paid Vs. Volunteer
  • Edit
• Partner Organizations
  • Option to change or not (Auto from last month)
• Churches
  • Option to change or not (Auto from last month)
• People Groups
  • Option to change or not (Auto from last month)
• Save data on each tab

• Look into how the module has been created thus far
• Look through the existing code to learn the conventions
• Create a view that shows up when someone clicks the 'Community' Tab Under the 'New Report'/'In Progress Report' section of the module.

Referencing Issue(s): #11

As a developer/ designer I need to research the pre-existing code of Hospital Run and understand it, so that I will be able to show a view when the Faith Declarations tab is clicked.

• Look into how the module has been created thus far - 1hr
• Look through the existing code to learn the conventions - 1hr
• Create a view that shows up when someone clicks the 'Faith Declarations' Tab Under the 'New Report'/'In Progress Report' section of the module. - 1hr

Referencing Issue: #20

As a developer I want to be able to research the current code of Hospital Run and generate a research doc, so that I can better understand the system for future use.

• Research the current functionality of HospitalRun - 30min
• Write up a research document stating findings - 1.5 hrs
• Put document in Cure/Research Folder in Google Drive
• Research Document

As a developer, I need to research the functionality of Hospital Run so that I can better understand Hospital Run and use Hospital Run as a reference for developing the ministry module.

• Research the current functionality of Hospital Run 45mins
• Write up a research document stating findings 2hrs 30mins
• Put document in Cure/Research Folder in Google Drive 3mins

obsolete

• Get Technology Stack working
• Download Ember Inspector from the Chrome Web Store
• Show that on your computer HospitalRun works
• Add your name to the Reports Archive (index) Template file in a paragraph tag to show that you have looked through the code, and have the tech stack working.
• Push changes up to server. (please make sure that your code it not broken!)

• Create a view

• Three Tabs

  Ministry Results	Recommendations/Needs	Other Significant Items
  3000 Word Text Entry Field	3000 Word Text Entry Field	3000 Word Text Entry Field

• Save Each Tab's Data

• Validate Data

Make it possible to print a monthly report to PDF.
This is a low priority issue, but its here so that we don't forget that there was a conversation about it.

Joel has asked that there's also a way to print out the reports

As a developer I want to be able to research the current code of Hospital Run and generate a research doc, so that I can better understand the system for future use.

• Research the current functionality of HospitalRun 1 hour
• Write up a research document stating findings 1.5 hour
• Put document in Cure/Research Folder in Google Drive
• Research Document

Community Events:

• Date
• Name
• Type
• Location
• Number of Pastors/Churches
• Number of Participants

Outreach/Community Events examples include Mobile Clinic, Outreach, Family & Patient Outreach

• Create View
• View all Events
• Edit Events
• Validate Events

Leadership Events

• Date
• Name
• Description of Topic
• Location

Auto total number of participants

Keep Track of Participants Data (Support partial Data)

• Name
• Organization/Church
• Gender
• Create Tab
• Create View
• Track Event Info
• Validate Events
• Add Participant
• Edit Participant

This is how you submit reports for inventory, and I would like to look into creating something similar to this when submitting the monthly reports.

The idea would be that we would have a list of "pages" that need to be completed before you are able to even click the submit button, and those would be green or red depending on completed or not (maybe checks and "x's") and each of those (buttons?) keeping track of validation would also be clickable so people could see what they needed to finish and they would be able to click what still needed to be finished.

@neongreenfruit

Reference: #77, #78

• Bedside Presentations
• Playroom Presentations
• Jesus Film
• Open Air Meetings
• Mobile Clinics
• More Opportunities

For Each Section:

• People reached
• Bibles Given out
• Totals for all
• Validation (numbers?)

obsolete

As a Cure Intern I need to get a base Ministry Module existing, so that when the team begins to work, there is something in place for them to build off of.

• Sub-Navigation in report (tabs??)
  • Copy New Patient Formatting (peter did this, still tweaking this)
  • Celtson added more sub navigation!
• Work through the top level navigation bar - 2 hours
• Set up Ministry Model - 10 hours

• Get Technology Stack working 17 hr
• Download Ember Inspector from the Chrome Web Store 3 minutes
• Show that on your computer HospitalRun works 5 minutes
• Add your name to the Reports Archive (index) Template file in a paragraph tag to show that you have looked through the code, and have the tech stack working. 30 minutes
• Push changes up to server. (please make sure that your code it not broken!) 5 minutes

As a developer/designer I need to have the static view layout of the faith declarations tab on Hospital Run, so that I can begin to work on the functionality of the view.

• Add fields for user to enter information - 30min
• Make sure not all data is mandatory - 15min
• Attach view to Faith Declarations tab - 15min

As a developer I need to be aware of the functionality that currently exists in HospitalRun so that I can implement efficient and consistent functionality across the module and the application.

• Research the current functionality of HospitalRun 1 hour
• Talk to Freddy about his thoughts 1 hour
• Talk to John about his thoughts 20 minutes
• Write up a research document stating findings 1 hour 40 minutes
• Put document in Cure/Research Folder in Google Drive

Total Hours: 4 hours

Research Document

As the Monthly Report Team's Documentation Expert, I need to keep track of the progress of the module, so that I can make sure that the project is going to get done on time.

• Create Documentation for out Module (as we go along) 11hrs

As a report I need an archive variable so that I can show up in the archived reports tab.

• Create Archive Variable 10 min
• Display archive reports on archive tab 1.5 hours
• Change In Progress Reports Page to only pull non-archived reports 45 min
• Create "Submit Function" to change Archive Variable (to true) 1.5 hours

Finish Part 2 before working on this
#80 #81

Reference: #38 and #39
@Falconvaulter and I will both be working on this.

(Moved from Sprint 3 to Sprint 4)

As a developer on the cure project I need to know how the technology stack works on my machine so that I can not only develop our application, but also understand how it all works on my specific machine.

• Get Technology Stack working - 8 Hours
• Download Ember Inspector from the Chrome Web Store - 10 minutes
• Show that on your computer HospitalRun works
• Add your name to the Reports Archive (index) Template file in a paragraph tag to show that you have looked through the code, and have the tech stack working - 5 minutes
• Push changes up to server. (please make sure that your code it not broken!) - 5 minutes

• Save the information to the database
• Be able to view all names that are in the database
• Be able the edit the names in the database

Referencing Issue: #20

As a User I need to be able to view all the unfinished reports so that I can select which one to edit

• Store New (unfinished report) in the "In Progress Report" Section 3 hours
• "In Progress Report" list on index page 1 hour @Falconvaulter
• Click report to load that specific report (By ID)
• Set archieved variable to False
• Keep report ID in in progress reports until submitted

Reference: #38 and #40

• Get Technology Stack working - 8 hours
• Download Ember Inspector from the Chrome Web Store < 1 hours
• Show that on your computer HospitalRun works 2 hours
• Add your name to the Reports Archive (index) Template file in a paragraph tag to show that you have looked through the code, and have the tech stack working. 2 hours
• Push changes up to server. (please make sure that your code it not broken!) < 1hours

As a developer I need to create a Christianity Explored Class view from the basis of the design document, so that the user can successfully navigate the view.

• Look into how the module has been created thus far 1 hour
• Look through the existing code to learn the conventions 1 hour
• Create a view that shows up when someone clicks the 'Christianity Explored' Tab Under the 'New Report'/'In Progress Report' section of the module. 3 hours

Referencing Issue: #12

• Must have a label

• Be able to Search through the database by name
• Make sure a filter function works for the New Believers - 5hrs

Referencing Issue: #20

As a developer, I need to create a view of the Summary tab so that others can understand the design and layout of the Summary tab.

• Look into how the module has been created thus far 1hr
• Look through the existing code to learn the conventions 2hrs 15mins
• Create a view that shows up when someone clicks the 'Summary' Tab Under the 'New Report'/'In Progress Report' section of the module. 6hrs 45mins

Referencing Issue(s): #13, #15, #16, #17, #18, #19, #21

• Get Technology Stack working
• Download Ember Inspector from the Chrome Web Store
• Show that on your computer HospitalRun works
• Add your name to the Reports Archive (index) Template file in a paragraph tag to show that you have looked through the code, and have the tech stack working.
• Push changes up to server. (please make sure that your code it not broken!)

obsolete

Staff Data:

• Create View
• Three Tabs

Meetings (Enter number of meetings, auto sum total)

• Entire staff Devotions
• Department Devotions
• Hospital Prayer Group Intercessions
• Spiritual Center Staff Meetings

• Save data on each tab
• Validate Data

Patient Data:

• Create View
• Create Tab

Playroom Activities examples include Playroom was active with more mothers than children, Bible Stories, Children’s movies, Design Making, Toys, puzzles and games like net ball, and Music cassettes

• Save data on each tab
• Validation

• Get project working on a Windows Machine
• Document how you did it (for the benefit of the other students as well as Cure)

• Get Technology Stack working 7 hours
• Download Ember Inspector from the Chrome Web Store 5 mins
• Show that on your computer HospitalRun works 5 mins
• Add your name to the Reports Archive (index) Template file in a paragraph tag to show that you have looked through the code, and have the tech stack working. 2 hours
• Push changes up to server. (please make sure that your code it not broken!) 10 mins

• Look into how the module has been created thus far
• Look through the existing code to learn the conventions
• Create a view that shows up when someone clicks the 'Leadership' Tab Under the 'New Report' section of the module.

Referencing Issue: #9

obsolete

• Research the current functionality of HospitalRun Id - 1 hour
• Write up a research document stating findings - 1 hour
• Put document in Cure/Research Folder in Google Drive - N/A

• Look into how the module has been created thus far
• Look through the existing code to learn the conventions
• Create a view that shows up when someone clicks the 'Patient' Tab Under the 'New Report'/'In Progress Report' section of the module.

Referencing Issue: #7

obsolete

As a developer I need to create and save a new ID for each report so that the data in each report can be linked to this report through the ID

• Look into how creating a new patient works (use this) - #43 (2 hours)
• Look at linking and Handlebars - 1 hour
• Create ID structure - for full reports - 8 hours

Reference: #39 and #40
@Falconvaulter

As a developer/designer I want to be able to generate an Additional Info view from the basis of the design document, so that the user can successfully navigate the view.

• Look through the existing code to learn the conventions - 30min
• Create a view that shows up when someone clicks the 'Additional Info' Tab Under the 'New Report'/'In Progress Report' section of the module. - 1hr
• Design the view accordingly. Follow Hospital Run conventions where necessary. - 1hr & 30min

Referencing Issue: #3

• Get Technology Stack working
• Download Ember Inspector from the Chrome Web Store
• Show that on your computer HospitalRun works
• Add your name to the Reports Archive (index) Template file in a paragraph tag to show that you have looked through the code, and have the tech stack working.
• Push changes up to server. (please make sure that your code it not broken!)

Backlog Creation:

• Spiritual Ministry Team - @BMaze, @Benning-k, @zmarkle
• New Believers Team - @ct1221, @TheFrontGuy
• Monthly Report Team - @Falconvaulter, @kp1251, @neongreenfruit

Team Meeting Hours:

Spiritual Ministry Team - 1 hour
New Believers Team - 1 hour
Monthly Report Team - 1 hour