Backlog Rework and Project Update

[Miguel-Alves]

The current status of Project Backlog is way different from the actual stage of Software, in a way that it does not trully reflect the work that needs to be done. So, We identified the urgent need of reworking and updating the entire Backlog.

We are going to review carefully every registered open issue to verify it's accuracy;
Run the project to find bugs or others inconscistencies;
And register every update on new issues, to make it clear the work that is being done;

.
Tasks

• Review carefully every registered open issue;
• Run the project to find bugs or others inconscistencies;
• Register every update on new issues;

Acceptance criteria

• Every registered open issue reviewed;

[mansogf]

I am currently checking the status of #95 #149 #76 #48 and will be working on these in the exposed order.

Checklist:

• Configurar CI/CD #95
• Remove all LAPPIS and TAIS info from code #149
• Document the new architecture #76
• Document API endpoit usage #48

The revision reports already made can be visualized on the issue page.

[Miguel-Alves]

So I am currently working on issues #145 #151 #150 #122;
I am going to review them and solve those that still describe a work that needs to be done;

[AmandaMuniz]

I am currently reviewing issues #113 #28 #114 #119

[luderibeiro]

I am currently reviewing issues #148 #67 #121 #115

[KalebeLopes]

I am currently reviewing issues #142 #100

[FranciscoHeronildo]

I am currently reviewing issues #144

[AmandaMuniz]

The issue #24 was checked on Feb 24 and was closed the same day.

[leticiaarj]

I am currently reviewing issues #146 #33 #29 #35.

[Miguel-Alves]

Issue #145 was maintained and solved on #161;
So it was moved to "Awaiting Review"

[Miguel-Alves]

Issue #151 was maintained, although it is a redundant work;

[Miguel-Alves]

Solved issue #151 as described in #162 . It was also moved to "Awaiting Review"

[Miguel-Alves]

Issue #150 was maintained, but has the same observation as issue #151;

[Miguel-Alves]

Solved issue #150 adding another validation to the button when editing utters, as described in #163 ;
Then, the issue was moved to "Awaiting Review"

[Miguel-Alves]

The Issue #122 was closed, because it did not represent a valid existing error.
@rodmaia did the check and closed the issue himelf.