Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Design change requests #440

Closed
21 tasks done
kasialanecka opened this issue Jan 11, 2018 · 3 comments
Closed
21 tasks done

Design change requests #440

kasialanecka opened this issue Jan 11, 2018 · 3 comments

Comments

@kasialanecka
Copy link
Contributor

kasialanecka commented Jan 11, 2018

IP Reporting

  • The need to include a “demo indicator table” in the Calculation Method Tab. Using an indicator as an example, the demo indicator table will enable the IP to see how the change of the calculation method for the sample indicator impacts progress reported across locations and reporting periods. This could provide an initial response to the challenge of setting the calculation method in a screen that is separate to the data entry screen.

  • In "Progress report" he default view must be overdue, send back and the next due report, but the partner should have the ability to select a view to show all reports.

  • Upon submission of the report - the email of the person submitting the report should be checked against the email of the authorized officer assigned to the PCA that is connected to that PD. If the emails are the same, then the report is submitted. If the emails are different, then there is a pop up that ask the user to select which Authorized Officer is the user submitting the report on behalf of. The user can choose only 1 and submit.

  • Add drilldown (expand the section) on the Progress report list page, the information should be the same as the PD details.

  • Add Locations to the PD Details page (add location SS)

  • Add Location filter to the Programme Document list Page.

  • Add a new column in the table (“Programme Documents” and “Progress Reports” pages) called “Report number”, where the report number is generated automatically. The last quarterly progress report (QPR) on the list should be called “final” QPR. The numbering of the reports will depend on the report type, e.g. Special reports would be SR1, Humanitarian will be HR1. The numbers will be generated at the time when the report is generated.

  • Standard Quarterly Progress Reports (QPR)

  • Humanitarian Reports (HR)

  • Special Reports (SR)

  • The Progress Reports List page needs to include a column and a filter to show reports by report type

  • The indicators page shows data reported for each indicator as per the latest and the previous reporting period

  • On the top of the page, the user must have the ability select to display only data reported in quarterly progress reports or humanitarian report through a checkbox or filter. This will ensure data shown in the indicator details tables is comparable. Data displayed should also be available in the export files (.pdf or .xls) as filtered on screen.

  • The need to include in the Programme Documents Details page any amendment (type and date) entered in PMP for reference to the UNICEF IP; No attachments from PMP will be shown though.

Cluster

  • [ x] NOT NEEDED: FTS data should also feature in the analysis section of PRP. In the analysis view we should be able to see a chart that shows % funded. The chart in our Analysis tab should show option 2 below.

  • There should be an “add more detail” button in the project details page

  • need an “add custom field” for any peculiar, additional information needed. Which could be clicked twice to add two fields - this might be a number/value or text. - in the project details page

  • Add baseline, target and in-need at location level in indicators

  • In adding/editing indicator locations, add a dropdown for “admin level” and all locations then are filtered at that admin level.

  • Adding in-need in indicators and UI changes in analysis and some other places where we show progress, to accommodate in-need as well.

  • Add a “indicator type” dropdown in cluster reporting > reports, so they are easy to find.

  • Add some helper text in indicator add/edit that makes some fields helpful. Make measurement specifications, means of verification optional. Baseline, target is optional as well.

@kasialanecka kasialanecka self-assigned this Jan 11, 2018
@kasialanecka
Copy link
Contributor Author

@rkrupinski please review

@kasialanecka
Copy link
Contributor Author

@chachra about tasks: "There should be an “add more detail” button in the project details page" - there is a button "edit" in Project details, can't this be used for this?

@kasialanecka
Copy link
Contributor Author

@chachra most of the tasks are completed, please review the Invision. With some mockups I would need some brainstorming, I will add comments/questions in Invison.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants