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.

Sign up for GitHub

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

Jump to bottom

Allow a different header label for the list of people on the place profile between different places in the hierarchy #4926

Closed
jillrshah opened this issue Oct 24, 2018 · 3 comments
Closed

Allow a different header label for the list of people on the place profile between different places in the hierarchy #4926

jillrshah opened this issue Oct 24, 2018 · 3 comments
Assignees
@ngaruko
Labels
Priority: 2 - Medium Normal priority Type: Improvement Make something better UI/UX Site design and usability improvements.
Projects
3.7.0

Comments

@jillrshah
Copy link

On a place profile, there is a header that describes the list of people in that place. For health systems where the lowest grouping in hierarchy is a family, this header is often "Family Members." However, it seems that this is the same for upper levels in the hierarchy as well. For example, the health center will then show the list of people presumably working at this health center as "Family Members." Of course, we can genericize this label such that it would be "People" but it's more ideal to be able to customize this label per hierarchy label.
@garethbowen
Copy link
Member

This could be related to the flexible hierarchy feature ( #3639 ).

@garethbowen
Copy link
Member

This should also be used for the button to create a new person:

screenshot from 2018-10-31 13-41-05

@garethbowen garethbowen mentioned this issue Feb 20, 2019
Closed
@garethbowen garethbowen self-assigned this Feb 20, 2019
@garethbowen garethbowen added UI/UX Site design and usability improvements. Priority: 2 - Medium Normal priority Type: Improvement Make something better labels Feb 20, 2019
@garethbowen garethbowen added this to To do in 3.5.0 via automation Feb 20, 2019
@garethbowen garethbowen moved this from To do to In progress in 3.5.0 Feb 20, 2019
@garethbowen garethbowen removed this from In progress in 3.5.0 May 5, 2019
@garethbowen garethbowen added this to To do in 3.7.0 via automation May 5, 2019
@garethbowen garethbowen moved this from To do to In progress in 3.7.0 May 5, 2019
@garethbowen garethbowen mentioned this issue May 6, 2019
Merged
@garethbowen garethbowen moved this from In progress to In AT in 3.7.0 May 22, 2019
@ngaruko ngaruko self-assigned this Jul 23, 2019
garethbowen added a commit that referenced this issue Aug 5, 2019
@garethbowen
Allow hierarchy levels to be configured
3258626 
- Adds a new property to app settings for contact_types which contains all translation keys, forms, icons, and other configurable properties as well as an ID to reference the type.
- Modifies all code that uses a hardcoded value to support the new configuration falling back to the hardcoded types where necessary.
- Removes hardcoded ContactSchema as well as ability to generate xforms from the schema. Contact creation/editing xforms now have to be manually provided, but as far as I'm aware everyone was already doing this.

#3639
#4926
#3570
@garethbowen
Copy link
Member

Done as part of #3639

3.7.0 automation moved this from In AT to Done Aug 5, 2019
@garethbowen garethbowen removed their assignment Aug 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ngaruko ngaruko

Labels
Priority: 2 - Medium Normal priority Type: Improvement Make something better UI/UX Site design and usability improvements.
Projects
No open projects
3.7.0
  
Done
Milestone
No milestone
Development

No branches or pull requests
3 participants
@garethbowen @ngaruko @jillrshah