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

Release 6.0 #1385

Open
12 of 54 tasks
vinayvenu opened this issue Sep 5, 2023 · 1 comment
Open
12 of 54 tasks

Release 6.0 #1385

vinayvenu opened this issue Sep 5, 2023 · 1 comment
Labels

Comments

@vinayvenu
Copy link
Member

vinayvenu commented Sep 5, 2023

May be - need clarification

No tasks being tracked yet.

Tech related - upgrades, tech tasks etc.,

  1. enhancement good first issue

Invoice related

No tasks being tracked yet.

To prevent tickets - for stability of app/bugs

  1. bug
    vinayvenu
  2. bug user reported
  3. bugsnag
    petmongrels
  4. bug
  5. bug user reported
  6. bug user reported
  7. bugsnag
  8. bug
  9. himeshr
  10. bug user reported
  11. bug
  12. enhancement good first issue
  13. bug
  14. bug
    BEULAHEVANJALIN Dinesh2019
  15. user reported

waiting list

No tasks being tracked yet.

Implementation easiness/time saving

  1. himeshr
  2. bug
  3. documentation
  4. Epic
  5. bug
@vinayvenu vinayvenu added the Epic label Sep 5, 2023
@github-project-automation github-project-automation bot moved this to New Issues in Avni Product Sep 5, 2023
@vinayvenu vinayvenu changed the title Release 7.0 miscellanous Release 6.0 miscellanous Sep 5, 2023
@mahalakshme mahalakshme changed the title Release 6.0 miscellanous Release 6.0 Sep 19, 2023
@mahalakshme
Copy link

Working on multiple branches at the same time with significant development effort going on in each branch causes - merge misses, merge conflicts (which may cause bug), commit to wrong branch, and general confusion.
At the same time working using developer effort to do QA is sub-optimal from quality of output perspective. Due to this we tend to start developing on new branch when older is not released to prod yet.

One thing we can do to alleviate this problem is to work on the following at the beginning of the release:

  • Dev Ops stuff which has been planned in the release upfront
  • Automated testing for stories that are planned in the release.

Some more details on automated testing and why we need to do it.
From long term sustainability of Avni codebase we need a better way to deal with complex codebase areas in Avni. Currently we either take a lot of time when working in this area, or avoid working in such areas, or make some hacky fix and move on. Ideally we should be having test and then refactor these code under the protection of these tests. In some cases also document.
These are the areas that I feel are complex in Avni.

Mobile App
Wizard
Search
Dashboard
Rule evaluation (not standalone usually mixed with others)
Sync
Individual dashboard
Approval flows
Checklist

Web App
Wizard, Form Designer

Avni Server
Sync
Identifiers
Direct Assignment
GroupSubject

Rule Server
Architectural problem

Media Viewer
Filtering, Paginated Display

Refactoring usually needed - too much logic in view, navigator, lot of duplication of code, large react/RN components or methods.

Refactoring usually needed - too much logic in view, navigator, lot of duplication of code, large react/RN components.

So I looked at the cards that are coming up in next release.

  • We could write test for Dashboard, Approval, and Server Sync (focussing on the area coming up)
  • Play the DevOps card

Server
avniproject/avni-client#1092 [Sync]

Mobile app
avniproject/avni-client#1101 [Dashboard]
avniproject/avni-client#1039 [Dashboard]
avniproject/avni-client#1045 [Dashboard]
avniproject/avni-client#1044 [Dashboard, Approval]
#1388 - [Approval]
avniproject/avni-client#971 - [Wizard]
avniproject/avni-client#1078 [Checklist]

DevOps
avniproject/avni-webapp#962

Identifier assignment not working as expected when an intermediate one is moved out of catchment · Issue #1092 · avniproject/avni-client
https://github.com

Filter Subjects by Date range filter doesnot return expected results always · Issue #1101 · avniproject/avni-client
https://github.com

@vindeolal vindeolal moved this from New Issues to Triaging analysis in Avni Product Nov 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

No branches or pull requests

2 participants