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

0.3.1 priorities #1672

Closed
ibolton336 opened this issue Jan 29, 2024 · 1 comment
Closed

0.3.1 priorities #1672

ibolton336 opened this issue Jan 29, 2024 · 1 comment

Comments

@ibolton336
Copy link
Member

ibolton336 commented Jan 29, 2024

  • Archetype assessment/Review status components on archetype table
  • Bugs around UI not reflecting required status for questionnaires.
    • Reports page landscape component
    • Application assessment status improvements.
      • Need to nail down expectation when application has archetypes when assessments have been completed, but archived.
      • Application status when ANY application assessment data exists should show application level status rather than archetype inherited status as it does now.
      • Need to coordinate with HUB to see if improvements can be made to further rely on the assessed boolean from archetypes when questionnaires are all marked as not required. Currently assessed is "true" when this case arises which feels like a bug.
  • Application tags dropdown improvements. Need to leverage new PF5 components to allow grouping of tags by category.
  • Have another look at table behavior when data is preloaded for filters from url. Current solution requires some customization that could potentially be baked into the table library.
  • Debug solution refinements for running analysis
  • Chips in sidebar is not sustainable. want a pre-filter for associated archetypes or applications
@ibolton336 ibolton336 changed the title 7.0.1 7.0.1 priorities Jan 29, 2024
@dymurray dymurray changed the title 7.0.1 priorities 0.3.1 priorities Jan 29, 2024
@sjd78
Copy link
Member

sjd78 commented Jul 18, 2024

@ibolton336 -- Can you update this issue based on the current version or close it?

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

No branches or pull requests

2 participants